BBFILES is whitespace delimited. If .= used, no whitespace padding is added around
the addition and this can lead to it being combined with some other part of the
field, leading to parts of BBFILES mysteriously not being seen.
For example, I have in my bblayers.conf:
/media/build1/poky/meta-intel/meta-emenlow \
/media/build1/poky/meta-intel/meta-fri2 \
/media/build1/poky/meta-intel/meta-jasperforest \
/media/build1/poky/meta-intel/meta-n450 \
/media/build1/poky/meta-intel/meta-romley \
and this results in the warning:
WARNING: No bb files matched BBFILE_PATTERN_fri2 '^/media/build1/poky/meta-intel/meta-fri2/'
and if I try to build MACHINE=fri2, I get strange errors due to the .bb files
not being parsed.
The fix is simply to use +=, just like every other layer.conf file.
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Add the linux-yocto-rt_3.8.bbappend for every BSP supporting RT.
Do not update BSPs maintained by ISG.
Built, booted, and sniff tested with:
$ cyclictest -p 90 -D 10m -t
on all platforms. All boot and complete the test without abnormal
outliers with the following exceptions:
o sys940x generated a panic, reported to rt-user. Possibly hw related.
o fri2 fails to boot, hanging at "i8042: No controller found"
These need additional investigation, but shouldn't delay the merge of
the recipes themselves.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
And specify the LINUX_VERSION corresponding to the kernel branch commits.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Now the v3.8 kernel recipes are available in the oecore & meta-intel layers.
And also the v3.8 kernel is validated for this BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Provide the jasperforest BSP specific extension for the linux-yocto_3.8
recipe from the oecore layer. This configures the right git branches of
the kernel repository for the jasperforest BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Provide the jasperforest BSP specific extension for the linux-yocto-dev
recipe from the oecore layer. This configures the right git branches of
the kernel repository for the jasperforest BSP.
This commit is addressing this bug:
[YOCTO #3931]
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Using AUTOREV turns out to cause problems with unreproducible
autobuilder builds and unwanted network access. This patch removes
kernel AUTOREVs and locks down SRCREVs and LINUX_VERSIONs.
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
The link has changed on the yoctoproject website, updating the URL
in the BSP layer READMEs.
This fixes the bug:
[Yocto #3730]
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Fixes parsing errors which is appearing after this commit to
meta-openembedded
http://cgit.openembedded.org/meta-openembedded/commit/?id=3c21a46020bd0816579648f684c41dbd6333583e
This triggers
exception NameError: name 'base_contains' is not defined
without this change
Avoid the immediate expansion operator (:=) which caused base_contains
added in the previous commit to fail to expand at the time the
meta-intel layer configs are parsed and replace it with one of the
append operators (.= or +=) that allows for delayed variable expansion.
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Acked-by: Tom Zanussi <tom.zanussi@intel.com>
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Add links in the readme so that one can find on the Internet
further details of the platforms supported by this BSP.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Instead of the denzil release specify the location of the source tarball
of danny release.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
To ease development on unreleased BSPs, let the kernel SRCREV float.
This avoids constantly having to update the SRCREVs manually, and
assures we won't get into a situation where LINUX_VERSION doesn't
match the version set by the kernel recipe.
We'll lock down the kernel SRCREVs and set the matching LINUX_VERSION
when we do releases, but in the meantime, we can use AUTOREV.
Note that individual BSPs are always free to override this maintain
their own SRCREVs if they want to.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Update all the linux-yocto .bbappends with the latest kernel SRCREVs
and add explicit LINUX_VERSIONs for the 1.3 release, to prevent a
mismatch between the kernel version actually used in the machine
branch vs the version the recipe uses for the kernel image, which can
change with stable updates.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
The WEBTITLE will be used to publish the BSP on the Yocto Project Website.
And adding the Yocto Project Compliance information for the 1.3 release.
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Keeping up2date with the latest HEADs of the branches
from kernel v3.4 repository
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
BSP maintainership for following BSPs is now transitioned from Tom to Nitin
sugarbay, emenlow, crownbay, jasperforest, chiefriver
Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Replaces all uses of PRINC with the form:
PRINC := "${@int(PRINC) + N}"
Where N is the previously assigned value plus one to ensure a
monotonically increasing PRINC value.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Acked-by: Tom Zanussi <tom.zanussi@intel.com>
CC: Saul Wold <sgw@linux.intel.com>
CC: Nitin Kamble <nitin.a.kamble@intel.com>
The xserver-xf86-config .bbappends are still using FILESPATH - update
them to use FILESEXTRAPATHS as recommended by the Poky Reference
Manual and BSP Developer's Guides.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
To pick up most recent changes, including the matching kernel changes
for the perf-scripting/perf-tui features.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
linux-yocto-2.6.37.bb was removed from oe-core, so remove the
corresponding .bbappend from meta-jasperforest.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Update the README.sources for all the meta-intel BSPs to reflect final
Yocto tarball location for denzil.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
The 3.0 based boards are lazy compared to our new modern ones.
Without this patch, the linux-yocto-3.0 kernel do_patch() task would
fail with:
/srv/home/pokybuild/yocto-autobuilder/yocto-slave/cedartrail/build/build/tmp/sysroots/x86_64-linux/usr/bin/updateme:
line 434: yocto/standard/cedartrail-standard.scc: No such file or
directory
Setting the KBRANCH explicitly avoids this issue. This brings the
following recipes inline with the fri2 and sys940x BSPs.
Fix proposed by Bruce Ashfield.
Testing: Built linux-yocto_3.0 for all machines involved, including the
nopvr, noemgd variants. All built linux-yocto_3.0 successfully.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
CC: Tom Zanussi <tom.zanussi@intel.com>
CC: Bruce Ashfield <bruce.ashfield@windriver.com>
CC: Kishore Bodke <kishore.k.bodke@intel.com>
These layers all contain machine configuration that depends on having
the meta-intel common layer enabled as well, so use LAYERDEPENDS in the
layer configuration for each one to make this explicit.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Based on community input, it might be more user-friendly to have some
basic information about submitting patches in the BSP README itself.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
The configuration that was being done in it is now forever redundant,
since it's enabled in oe-core.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
The affected BSPs now need to access common metadata in locations off
of the top level of meta-intel, so need to add meta-intel itself to
their layer configuration. This updates the READMEs for those BSPs to
mention that.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
There's nothing in meta-intel/common used by jasperforest any longer,
and is too broad anyway, so remove it from BBFILES.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
