Tom Zanussi [Wed, 17 Dec 2014 00:41:04 +0000 (18:41 -0600)]
yocto-bsp: Get rid of 'strange' filenames in mips templates
For the mips templates, give all the 'strange' yocto-bsp template
filenames 'normal' names, adding new yocto-bsp-filename and
yocto-bsp-dirname tags for the new filename processing pass where
needed.
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Tom Zanussi [Wed, 17 Dec 2014 00:41:03 +0000 (18:41 -0600)]
yocto-bsp: Get rid of 'strange' filenames in x86 templates
For the x86 templates, give all the 'strange' yocto-bsp template
filenames 'normal' names, adding new yocto-bsp-filename and
yocto-bsp-dirname tags for the new filename processing pass where
needed.
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Tom Zanussi [Wed, 17 Dec 2014 00:41:01 +0000 (18:41 -0600)]
yocto-bsp: Get rid of 'strange' filenames
Give all the 'strange' yocto-bsp template filenames 'normal' names,
adding new yocto-bsp-filename and yocto-bsp-dirname tags for the new
filename processing pass where needed.
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Tom Zanussi [Wed, 17 Dec 2014 00:41:00 +0000 (18:41 -0600)]
yocto-bsp: Add a processing pass to get rid of 'strange' filenames
Operating systems that can't handle filenames containing anything but
uppercase letters don't like to see 'strange' characters in filenames
such as the file and directory names yocto-bsp uses as part of its
templating mechanism. To fix this, we essentially add another level
of metadata into the template files themselves rather than into their
names, and add a processing pass that internally gives us what we had
before. Specifically:
- strange characters in filenames are moved inside the files they
apply to, to the first line of the file prepended with '#
yocto-bsp-filename {{...}} filename | this'
- strange characters in directory names are moved inside a new file
of the same name but ending in .noinstall and with the first (and
only) line of the file prepended with '# yocto-bsp-dirname {{...}}
dirname'
If the new filename contained in the yocto-bsp-* tag is 'this', the
filename is the existing name of the file. For a dirname, this would
be the filename with .noinstall removed.
"Fixes" [YOCTO #5312].
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Otavio Salvador [Tue, 9 Dec 2014 14:23:56 +0000 (12:23 -0200)]
distro/poky: Add Debian 8 (Jessie) as sanity tested
The Debian 8 (codename Jessie) is frozen and has been in use in our
machines for some time. It has been working fine and as it is about to
be released it is better to whitelist it and remove the ugly warning
from build logs.
Signed-off-by: Otavio Salvador <otavio@ossystems.com.br> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Aníbal Limón [Fri, 28 Nov 2014 01:10:47 +0000 (19:10 -0600)]
package_regex.inc: Update REGEX'es in order to find upstream versions correctly
Since Bitbake fetcher implements latest version string methods using bs4 to parse
HTML data some regexes need update because bs4 gives functionality to get href
entries and isn't necessary put pattern [hH][rR][eE][fF] into it, this make
maintenance easier.
Compatibility testing was made running distrodata class and the result files
can be found at:
Robert Yang [Mon, 20 Oct 2014 03:35:41 +0000 (20:35 -0700)]
local.conf.sample.extended: update for RPM_PREFER_ELF_ARCH
Updated as the rpm upstream suggested:
- RPM_PREFER_COLOR -> RPM_PREFER_ELF_ARCH
- 3 -> 4
Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Armin Kuster [Thu, 21 Aug 2014 22:16:44 +0000 (15:16 -0700)]
nettle: add nettle to tracking
add note on regarding nettle upgrade
V2: add missing '_pn'
: more description.
Nettle version 3.0.0 breaks gnutls build do
to api changes. Updating to nettle 3.0 is on
gnutls roadmap
https://www.gitorious.org/gnutls/pages/Plan3_4
Signed-off-by: Armin Kuster <akuster808@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Robert Yang [Thu, 31 Jul 2014 06:06:16 +0000 (23:06 -0700)]
local.conf.sample.extended: update for preferred ABI
[YOCTO #4073]
Signed-off-by: Robert Yang <liezhi.yang@windriver.com> Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake.conf: move BB_NUMBER_THREADS and PARALLEL_MAKE to bitbake.conf
Currently, BB_NUMBER_THREADS and PARALLEL_MAKE default to unset and
are set in local.conf. Now that we have the automatic probing,
the default values can be set in bitbake.conf and an example of
explicitly defining how many tasks to run can be moved to
local.conf.sample.extended.
[YOCTO #6217]
Signed-off-by: Roxana Ciobanu <roxana.ciobanu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
oeqa/controllers/beaglebonetarget.py: fix deploy when kernel file is a broken link
Sometimes the uncompressed rootfs image contains boot/uImage but if it's a symlink, it seems broken from the master image's point of view.
Because [ -e /mnt/testrootfs/boot/uImage ] will return 1, it will proceed to copy the backup kernel file over it but cp ~/test-kernel /mnt/testrootfs/boot/uImage will also fail with:
cp: not writing through dangling symlink
Adding a new check here, if the boot/uImage is a link, leave it as is.
Signed-off-by: Corneliu Stoicescu <corneliux.stoicescu@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Kevin Hao [Tue, 17 Jun 2014 16:13:20 +0000 (12:13 -0400)]
mpc8315e-rdb: add the example about booting from jffs2 root
Signed-off-by: Kevin Hao <kexin.hao@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Kevin Hao [Tue, 17 Jun 2014 16:13:19 +0000 (12:13 -0400)]
mpc8315e-rdb: add the jffs2 image support
There is a 32M NAND flash on this board, so it would be convenient
that a jffs2 image is created by default. Also change the default image
type from "tar.gz" to "tar.bz2" in order to be compatible with
the beaglebone black and edgerouter BSP.
Signed-off-by: Kevin Hao <kexin.hao@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Kevin Hao [Tue, 17 Jun 2014 16:13:18 +0000 (12:13 -0400)]
mpc8315e-rdb: bump to linux-yocto 3.14
Signed-off-by: Kevin Hao <kexin.hao@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Paul Barker [Wed, 28 May 2014 15:19:50 +0000 (15:19 +0000)]
package_ipk.bbclass: Support hierarchical feed
This patch allows for an optional new layout for ipk feed directories which I've
called a 'hierarchical feed' and is based on how Debian pools package files. It
is disabled by default and is enabled by setting IPK_HIERARCHICAL_FEED to "1".
In the traditional feed layout, package files are placed in <outdir>/<arch>/.
This can lead to several thousand files existing in a single directory which is
often a problem if developers want to upload a package feed to a shared web
hosting provider. For example, in my case, listing files via FTP only shows the
first 2000 files, breaking my scripts which attempt to upload only new and
changed files via FTP.
In the hierarchical feed, package files are written to
<outdir>/<arch>/<pkg_prefix>/<pkg_subdir>, where pkg_prefix is the first letter
of the package file name for non-lib packages or "lib" plus the 4th letter of
the package file name for lib packages (eg, 'l' for less, 'libc' for libc6).
pkg_subdir is the root of the package file name, discarding the version and
architecture parts and the common suffixes '-dbg', '-dev', '-doc', '-staticdev',
'-locale' and '-locale-*' which are listed in meta/conf/bitbake.conf.
This change relies on recent patches to opkg-utils which support hierarchical
package feeds.
Signed-off-by: Paul Barker <paul@paulbarker.me.uk> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This variable is a left-over from early glibc recipes.
It is not referenced anymore in oe-core, and its functionality
has been replaced with 'GLIBC_GENERATE_LOCALES'.
Also remove the reference to it in local.conf.sample.extended.
Signed-off-by: Jacob Kroon <jacob.kroon@mikrodidakt.se> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The FILESEXTRAPATH was not getting used correctly since our distro
OVERRIDE is for poky-tiny, not poky, so just remove it, also we are
not using a version directory so ensure we get correct BPN (Base Package
Name).
[YOCTO #6353]
Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
oeqa/controllers/beaglebonetarget.py: fix conditions for files copied to /boot
Using '[ ! -e /mnt/testrootfs/boot/uImage ] && cp ~/test-kernel /mnt/testrootfs/boot/uImage' would result in exit code 1 if the first condition is not met.
Changing the code to return exit status 0 if /mnt/testrootfs/boot/uImage exists.
Bruce Ashfield [Fri, 9 May 2014 20:50:04 +0000 (16:50 -0400)]
README: add maintainers section for hardware reference boards
Kevin Hao has stepped up to take care of issues specific to the meta-yocto-bsp
hardware reference boards. I'll also serve as a maintaier, so adding my name
as well.
To make this clear, let's add it to the README.hardware file that describes
the boards.
cc: Kevin Hao <kexin.hao@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Based on BeagleBoneTarget, this provides support for deploying images
and running tests on an EdgeRouter Lite (edgerouter). The device must
be set up to boot into the master image already - see the instructions
in the file.
Implements [YOCTO #6253].
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
With a serial connection and beaglebone setup correctly as per
README.hardware (nand erased, default uboot config assumed, etc) and a
correctly deployed core-image-testmaster, we could actually deploy and
test AB built images.
In the default configuration u-boot will do the right thing and will
always boot into the master image (rootfs on second fs on the card,
kernel in /boot on the same partition). We just need to tell it for the
test image to use the third partition and update the kernel cmdline.
Pexpect is used to interact with whatever serial connection we have
(which for this target is mandatory).
There is some handling for images that don't contain the kernel and
dtb files as needed (such as core-image-minimal).
Implements [YOCTO #6252].
Signed-off-by: Stefan Stanacar <stefanx.stanacar@intel.com> Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Added new package data and resorted per
http://article.gmane.org/gmane.linux.embedded.poky/9253
Removed -native packages as distrodata handles them in OVERRIDES.
However, meta packages and grub-efi are special and needs some
handling within distrodata. I have a patch for this but for the
release I'm leaving them within distro-alias.
Signed-off-by: Beth Flanagan <elizabeth.flanagan@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Use fbdev video driver for xserver-xorg
* Recommend installing device tree DTB files into rootfs /boot directory
* Switch back to uImage kernel format from zImage, as U-boot was not updated
- default has changed to zImage in newer U-boot 2013.10+, but we use 2013.07
* Correct copy/paste typo in serial console
Signed-off-by: Denys Dmytriyenko <denys@ti.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bruce Ashfield [Wed, 9 Apr 2014 19:41:32 +0000 (15:41 -0400)]
edgerouter: clarify diskboot instructions
There was some missing details in how to boot from the edgerouter USB
storage. With this update, we have the information required to boot from
either the vfat, or ext3 partition.
[YOCTO #6113]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Yang Wei [Mon, 31 Mar 2014 18:01:59 +0000 (14:01 -0400)]
poky: add edgerouter information to README.hardware
Adding the summary, preparation and boot information for the newly introduced
edgerouter BSP.
Signed-off-by: Yang Wei <Wei.Yang@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Yang Wei [Mon, 31 Mar 2014 18:01:57 +0000 (14:01 -0400)]
yocto-bsps: Add a new BSP to support edgerouter
The EdgeRouter Lite is part of the EdgeMax series. It is an MIPS64 router(Cavium Octeon)
with 512MB of RAM, which uses a USB pendrive for storage.
Setup instructions
------------------
You will need the following:
* NFS root setup on your workstation
* TFTP server installed on your workstation
* Straight-thru 9-conductor serial cable (DB9, M/F) connected from your
PC to UART1
* Ethernet connected to the first ethernet port on the board
The rest of the details can be found in the BSP kernel config, and README.hardware.
Signed-off-by: Yang Wei <Wei.Yang@windriver.com> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
projects / thirdparty / openembedded / openembedded-core-contrib.git / log
