Update the yocto hardware reference platform to use the
3.4 kernel by default.
This platform is supported in mainline, so no patch carry
forward or similar is required. Tested via NFS booting the
kernel on real hardware with 3.4.1 and things just work as-is.
(From meta-yocto rev: fbe1be490172993140db31472d14652d8ed45624)
Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Romania team performed package maintainers modification
based on relevant experience and expertise area assignement.
No entries outside Ro team were touched.
(From meta-yocto rev: 39a68249e561f7e36f1819769719f35f62c1f3d2)
Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Manually checked packages for updates.
Changed the necessary fields with updated values.
Added missing recording where necessary.
Beautified some packages info.
Removed small typos in distro_alias.inc and recipe_color.inc.
All changes easy detectable in the diff.
(From meta-yocto rev: 387445c38b5eec0fad9dc8a819cedd5d89171c17)
Signed-off-by: Cristian Iorga <cristian.iorga@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updated gzip and sudo to reflect recent recipe upgrades.
Updated manual check information for e2fsprogs, chrpath, opensp,
expat, nfs-utils, and libpng.
(From meta-yocto rev: eb52c5988e67adb1f6843da83f3ffe8bccda207b)
Signed-off-by: Scott Garman <scott.a.garman@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(-) rename it also in maintainers.inc
[YOCTO #2636]
(From meta-yocto rev: eabf9a60e6b56a9074319e5216119c03a76e44ba)
Signed-off-by: Valentin Popa <valentin.popa@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The only bit we seem to need from the linux-yocto include is the
SRCREV_FORMAT. If we define this explicitly, we can avoid including the
linux-yocto include.
This is desirable so that linux-yocto can require kernel and simplify
the PR update process of all the linux-yocto* recipes. Pulling in
kernel to the linux-libc-headers-yocto recipes causes build failures by
pulling in "update-modules-nativesdk".
(From meta-yocto rev: be73421c4c8f5ae119aa8c030cca2442087d5c22)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Add the option to filter packages according to license.
[YOCTO #2473]
(From meta-yocto rev: 156147991dc1ec7f58ac355b8e0f430958de2831)
Signed-off-by: Xiaofeng Yan <xiaofeng.yan@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Currently poky-tiny images will boot and run /bin/sh, which results in
error messages to the console about being unable to open the tty and job
control being disabled.
The shell must be session leader to open the tty, and the tty must not
be /dev/console (it should be a vt or a physical tty like ttyS0), the
tty is required for job control (handling signals, etc.).
The goals of poky-tiny are to be an initial starting point from which to
build a distribution that does what you want, and NOTHING more.
This patch results in a system that boots with the virtual filesystems
mounted, the local network interface up, and a shell with job control
running, and a hook (/etc/rc.local) for easy customization. Nothing
else.
Enabling the basic busybox init, including the ability to give the
controlling console to commands starting with a dash in inittab results
in a 5664 byte delta (compared with 2560 bytes for enabling setsid and
cttyhack). Note that the help in busybox suggests the cttyhack may be
more reliable than the init support for handing over the controlling
terminal.
So the difference between using a standard init and just enabling the
two options is about 3k, but enabling setsid and cttyhack may enable
others to things besides what I am looking to do. Enabling init in both
DISTRO_FEATURES and busybox is fairly trivial to do, so I think it's
better to leave that as something to add if needed, rather than
something to remove, as that is more consistent with the goals of
poky-tiny.
Thanks to Tim Bird for his suggestion to include support for rc.local by
default.
(From meta-yocto rev: 5ae60ed46b34cbf4ab17fe7eab3d46e2f78ee7b8)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Tim Bird <tim.bird@am.sony.com>
CC: Thomas Frydrych <tf+lists.yocto@r-finger.com>
CC: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
CC: Paul Eggleton <paul.eggleton@linux.intel.com>
CC: Phil Blundell <philb@gnu.org>
CC: Khem Raj <raj.khem@gmail.com>
CC: Koen Kooi <koen@dominion.thruhere.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
When building very small systems, it can be useful to spawn a shell from
a simple init script, rather than a full System V Init process. This
requires the shell be the session leader and be able to open the
controlling terminal if it is to have job control.
Create a busybox bbappend in meta-yocto with a poky-tiny/defconfig.
This adds SETSID and CTTYHACK for poky-tiny on top of the oe-core
defconfig.
(From meta-yocto rev: 04842688748f58966be533ed6ebc95a19190a31c)
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Tim Bird <tim.bird@am.sony.com>
CC: Thomas Frydrych <tf+lists.yocto@r-finger.com>
CC: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
CC: Paul Eggleton <paul.eggleton@linux.intel.com>
CC: Phil Blundell <philb@gnu.org>
CC: Khem Raj <raj.khem@gmail.com>
CC: Koen Kooi <koen@dominion.thruhere.net>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Remove VERSION and CHECK_DATE info for packages we can generate
the information for automagically.
Manually checked:
console-tools
sysfsutils
cracklib
less
psmisc
sysstat
glew
libmad
boost
libcheck
libcap
libexif
sqlite3
Upgraded:
sqlite3: Update to 3.7.13
psmisc: Update to 22.19
sysstat: Update to 10.0.5
util-linux: Update to 2.21.2
libxml2: Update to 2.8.0
mx: Upgrade to 1.4.6
libxml-simple-perl: Upgrade to 2.20
cracklib: Upgrade to 2.8.19
resolvconf: Upgrade to 1.67
libtasn1: Upgrade to 2.13
gnutls: Upgrade to 2.12.20
foomatic-filters: Upgrade to 4.0.16
libidn: Upgrade to 1.25
libtiff: Upgrade to 4.0.2
(From meta-yocto rev: 5d2f68863a7684eab4f6d3cb0054cdc26b50dd11)
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the linux-libc-headers-yocto recipe to 3.4. There are blocks
of code and definitions that are handled by the included libc-headers.inc,
so we shouldn't be repeating them in this recipe.
(From meta-yocto rev: ad8456e013907c444d972ad945b8d6e96be1d4f0)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The arch mapping done in kernel-arch should be used instead of
recipe local mapping. Inheriting kernel-arch consolidates the
code and simplifies the libc-header recipe.
(From meta-yocto rev: 4978935df1c59afdaeeb2f975647d4b6c9b7a9c3)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Many people are seeing issues from the empty path warnings from BBPATH.
The empty path entry corresponding to the current working directory is a
problem since if cwd changes, so does BBPATH and build reproducibility.
Simply removing the empty element causes problems since the build
directory then isn't listed in BBPATH which means local.conf isn't found
and this gives an extremely confusing error message about bbappends
being unsatisfied.
The build directory in bitbake terms is TOPDIR. The correct way to fix
things is to add in TOPDIR into bblayers.conf itself. This means the
layers can happily append/prepend to BBPATH at will as its no longer
empty hence neatly solving all the various problems. Since the file has
changed, the version is also changed.
(From meta-yocto rev: 7bbbedf64b0820cacffe723789486d3081894827)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Updating the 3.4 SRCREVs to pickup a yaffs2 update and the removal
of a feature that was required in the 3.2 kernel tree.
1/2 [
meta: rc6: remove rc6 patches for snb
The sandybridge rc6 patches are part of the released v3.4 kernel.
Hence there is no need to keep these patches in the 3.4 linux
yocto kernel repository.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
]
2/2 [
yaffs2: update core support
Uprev yaffs2 to latest version as of 2012-05-29
]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This patch creates a split up of the orignal distro_tracking_files
since we need to manage this more in the meta-yocto space, each
file has a set of comments describing the contents
maintainers.inc is a list of the maintainers
recipe_color.inc is a burn down list of recipes that need to be checked
recipe_data.inc contains data for creating the BOM and tracks some
info that could be moved into the recipes directly.
upstream_tracking.inc: Version and Date information that can not be
discovered automagically.
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The update from v3.0.24 to v3.0.32 removed a lock that the routerstationpro
BSP was using, and broke the build.
Updating the SRCREV to pickup a fix for the new lock and fix the board
build.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The 3.4 kernel is available and has been built and booted on
all the qemu machines, so it now becomes the default for the
qemu machines, and machines that don't explicitly set a preferred
version.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Picking up the oe-core commit:
Bumping the 3.2 SRCREVs to pickup the following configuration changes for
the new chiefriver BSP and the existing fri2 machines:
5b4c9dc fri2: update base config
cdfbb50 fri2: add usb-mass-storage to standard and preempt-rt
3c1af06 fri2 update: drop NETDEVICE, e1xxx, usb-mass-storage, add iwlwifi feature
26a4d79 iwlagn: Correct a comment typo
ade9c57 iwlwifi: Add a feature for iwlwifi
571b6cb fri2: Configuration update (usb, wifi, i2c)
b257485 meta: add tmp/rc6 feature
24c6494 chiefriver: create initial BSP infrastructure
All branches are also updated with the following fix:
1ce6700 efi: Add patch to fix 32bit EFI service mapping (rhbz 726701)
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Creating the initial meta-yocto bbappend for the 3.4 kernel.
The routerstationpro and beaglboard are not initially marked as
compatible since full testing has not completed. Future updates
will remove this restriction.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
To avoid mapping machine names to kernel machine names in recipes,
we can define multiple KMACHINE names for a single in tree board.
This allows the tools to match a board description to multiple
different MACHINEs.
As a result, we can remove the explicit KMACHINE mappings from
the linux-yocto recipes and allow the KMACHINE=${MACHINE} default
to handle mappings. Individual recipes an bbappends can override
this as required.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
With the introduction of the 3.4 kernel, the 2.6.37 kernel recipe is
removed, so we'll also remove the meta-yocto 2.6.37 bbappend.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Change the usage about arhiver.bbclass due to the improvement for
usability of archiver.bbclass
[YOCTO #2472]
Signed-off-by: Xiaofeng Yan <xiaofeng.yan@windriver.com>
A major effort was completed as part of 1.2 to fix many WARNING
messages, change the level of those fixed areas to ERROR so we
do not backslide on our quality level
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Updates to the kern-tools to be more flexible and support multiple
upstream repository formats means that KMACHINE should really only
map to a machine and that KBRANCH should specify branch information.
To adapt to this change, we split the hardware reference boards into
KMACHINE and KBRANCH mappings.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Bumping the routerstationpro SRCREV for the following fix:
mm/msync: tweak tmpfs patch for syscall msync
Commit 1c3ae5441 "mm: msync: fix issues of sys_msync on tmpfs"
fixes the problem that sys_msync fails with tmpfs on MIPS CPU which
has feature "cache alias".
But it makes POSIX test cases mlockall/3-6 3-7 fail on MIPS.
Case mlockall/3-6 creates a share memory, and maps it to memory.
fd = shm_open(SHM_NAME, O_RDWR|O_CREAT, S_IRUSR|S_IWUSR);
foo = mmap(NULL, BUF_SIZE, PROT_WRITE, MAP_SHARED, fd, 0);
Then calls mlockall to lock all of the virtual address space:
if (mlockall(MCL_CURRENT) == -1) {
At last tests whether the virtual address spaces are locked:
page_ptr = (void*) ((long)foo - ((long)foo % page_size));
result = msync(page_ptr, page_size, MS_SYNC|MS_INVALIDATE);
It espects msync returns -1 with EBUSY but returns 0.
Case mlockall/3-7 creates a normal file to mmap, and it fails too.
Tweak the patch to:
1 Moved the CONFIG_TMPFS block down in the loop so that the normal
vma flag checking will perform.
2 There may be other VMAs in the list after this VMA which belongs
to tmpfs file, and we should sync them after the tmpfs one. So
remove the break loop clauses.
Signed-off-by: Kang Kai <kai.kang@windriver.com>
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Since it is an LTS release, the final version string was not
"Ubuntu 12.04" but "Ubuntu 12.04 LTS", so use this when doing the tested
host distribution check.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
After the recent gettext dependency fix (commit 6e5cb40dfa
"gettext.bbclass: Ensure we don't overwrite other DEPENDS_GETTEXT values",
its no longer necessary to have to have these options to build meta-toolchain.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Specify a list of tested host distributions, based on those tested prior
to the Yocto Project 1.2 release. This will enable a warning to be
printed upon starting bitbake if the host distribution is not one on the
list.
Note: this warning is intended to help new users; if you are receiving
this warning and wish to disable it, just add SANITY_TESTED_DISTROS = ""
to your local.conf.
Fixes [YOCTO #1096].
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This fixes bug [YOCTO #2295]
eglibc needs libc-posix-regexp-glibc & libc-libm-big enabled in its
configuration to avoid following eglibc build issue. Thanks to
Nitin for identifying the required features.
...
| In file included from xregex.c:634:0:
| xregex.c: In function 'byte_regex_compile':
| xregex.c:3395:8: error: too few arguments to function 'findidx'
| ../locale/weight.h:23:1: note: declared here
...
The libc features added to support building meta-toolchain add 461KB to the C
libraries. 320KB directly to libc (a 32% increase in size). If not building
meta-toolchain, the user should be able to easily configure these out.
Create a new variable to capture these dependencies,
DISTRO_FEATURES_LIBC_TOOLCHAIN, keeping them separate from the core tiny
requirements. Make it clear how to disable these if meta-toolchain is not
needed.
This patch has been tested by running the following for the qemux86 machine with
DISTRO=poky-tiny:
$ bitbake -c cleansstate eglibc
$ bitbake meta-toolchain
$ bitbake core-image-minimal
The libc comparisons were made from core-image-minimal ext2 filesystems build
before and after the applicaiton of this patch and Nitin's previous poky-tiny
libc features patch in support of meta-toolchain:
commit 8c48ab6183
Author: Nitin A Kamble <nitin.a.kamble@intel.com>
Date: Mon Apr 9 15:15:01 2012 -0700
poky-tiny.conf: adjust eglibc options for poky-tiny
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Nitin A. Kamble <nitin.a.kamble@intel.com>
CC: Saul Wold <sgw@linux.intel.com>
CC: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The ABI version definition should go along with the DISTRO variable
since it impact the TMPDIR definition.
Otherwise, if a user used to work with pure OE-Core, and then he/she
added meta-yocto layer, it will report ABI version incompatibility
issue. This is because ABI is changed to "8" by adding meta-yocto layer,
however the DISTRO variable is not defined and TMPDIR is still
"tmp-eglibc".
Defining the OELAYOUT_ABI variable in poky.conf could fix this issue.
This fixes [YOCTO #2303]
Signed-off-by: Dongxiao Xu <dongxiao.xu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
commit 8cd31f9b0 linux-yocto/meta-yocto: update hardware reference boards to v3.0.24
Missed a merge commit on the hardware reference BSP branches.
As a result, validate_branches is adjusting the tree to build the
proper SRCREV. For machines with board specific commits this means
that some of their commits are missing, which leads to boot failure.
Bumping the SRCREVs fixes the problem
Fixes [YOCTO: #2292]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
The meta-yocto hardware reference boards missed a SRCREV update when the
base recipe when to v3.0.24. This updates the SRCREVs to ensure that the
kernel that is built and booted matches the version information conveyed
from the base recipe.
Fixes [YOCTO #2265]
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Here is the message from the bug 2260:
meta-yocto/conf/machine/beagleboard.conf hardcodes the virtual/xserver
provider, i.e., it includes the following:
PREFERRED_PROVIDER_virtual/xserver = "xserver-xorg-lite"
I don't think machine conf is the correct place for selecting what is
essentially a distro feature, but at least this should use the '?='
operator; as is to select a different provider one must provide a
complete beagleboard.conf file.
[YOCTO #2260]
Signed-off-by: Robert Yang <liezhi.yang@windriver.com>
With the move to 3.2 from 3.0 in oe-core, the 3.0 no longer exists.
Prefer 3.2 instead.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
linux-libc-headers-yocto is not directly required in meta, so we can
safely move it to meta-yocto.
Machines including meta-yocto that are using linux-yocto that need headers
which are completely up to date with the linux-yocto git tree can use this
as their preferred linux-libc-headers.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This is an update of the linux-yocto 3.0 and 3.2 SRCREVs to bring
in the following updates:
- v3.0.23 stable update
- v3.2.9 stable update
- 3.0/3.2: fri2 updates (pch + configuration changes) from Darren Hart
- 3.0: pvr merge from Kishore Bodke
- linux-yocto/rt: update to 3.0.23-rt38
- linux-yocto/rt: update to 3.2.9-rt15
These have been built for all qemu targets, and built for the appropriate
hardware platforms.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Paul Gortmaker
Saul Wold
Alexandru DAMIAN
Cristian Iorga
Scott Garman
Richard Purdie
Valentin Popa
Darren Hart
Xiaofeng Yan
Bruce Ashfield
Paul Eggleton
Tom Zanussi
Dongxiao Xu
Robert Yang
Nitin A Kamble