| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
Update linux-yocto_3.0 kernel SRCREVS for crownbay, fishriver, fri2,
jasperforest, and sugarbay.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
|
|
|
| |
Update linux-yocto_3.0 kernel SRCREVS for crownbay, fishriver, fri2,
jasperforest, and sugarbay.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
|
|
|
| |
Update linux-yocto_3.0 kernel SRCREVS for crownbay, fishriver, fri2,
jasperforest, and sugarbay.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
|
|
|
| |
Update linux-yocto_3.0 kernel SRCREVS for crownbay, fishriver, fri2,
jasperforest, and sugarbay.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
|
|
|
| |
Update linux-yocto_3.0 kernel SRCREVS for crownbay, fishriver, fri2,
jasperforest, and sugarbay.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
|
|
|
| |
Update linux-yocto_3.0 kernel SRCREVS for fishriver, fri2,
jasperforest, and sugarbay.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
|
|
| |
Update 3.0 kernel SRCREVs for fishriver, fri2, jasperforest, sugarbay.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
|
|
|
|
|
|
| |
As the all the BSPs use the same BSP branch and meta commit ID as the base
recipe, there is no need specify the KBRANCH and SRCREVs. Not doing so
greatly simplifies maintenance. Leaving the syntax in place, but commented
out, serves as documentation should the need arise to use a different BSP
branch or meta commit ID.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
|
|
|
|
|
|
| |
All the BSPs build out of the preempt-rt/base branch (rather than a
preempt-rt/$MACHINE branch), so separate KMACHINE and KBRANCH assignments are
required for each BSP.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
|
|
|
|
|
| |
Switch fishriver to the 3.0 kernel, lock it down, and update kernel
SRCREVs.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
| |
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The linux-yocto recipes have been renamed to include explicit
version numbers. The meta-intel bbappends must be updated to
follow the new naming convention.
As a consequence of the recipe renames any SRCREV specificiations
that were part of a machine.conf have been moved to the corresponding
bbappend file. This allows the 2.6.34 and 2.6.37 SRCREVs to co-exist.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
Minor whitespace cleanup.
Remove inadvertant? linux-libc-headers provider change.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
|
|
|
|
|
|
|
| |
The fishriver BSP was borrowing a few things from crownbay, but now
has its own branch, so remove the crownbay-specific items.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
My previous commit used a self referencing immediate expansion assignment using.
This causes a circular reference and build failure, particularly when more than
one layer is configured in.
Use the _prepend mechanism in conjunction with the immediate expansion
assignment operator to accomplish a similar thing without the self referencing.
Note: This patch is dependent on changes to oe-core, specifically:
http://lists.linuxtogo.org/pipermail/openembedded-core/2011-May/003145.html
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Cc: Tom Zanussi <tom.zanussi@intel.com>
Cc: Phill Blundell <pb@pbcl.net>
Cc: Koen Kooi <koen@dominion.thruhere.net>
|
|
|
|
|
|
| |
And add linux-yocto-stable bbappend.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Clobbering FILESEXTRAPATHS prevents multiple bbappend files providing file://
SRC_URIs. Extend the variable in each meta-* layer instead.
Build tested with linux-yocto on n450 and crownbay and linux-yocto-stable on
crownbay. Build tested linux-yocto on n450 with a third layer adding a config
fragment.
Signed-off-by: Darren Hart <dvhart@linux.intel.com>
Acked-by: Tom Zanussi <tom.zanussi@intel.com>
|
|
This layer provides support for Z530 + EG20T Intel systems.
Currently it supports only vesa graphics, which will be upgraded
shortly.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
|