ia32-base.inc no longer contains everything these BSPs need - some of
what was in that file is now in meta-intel.inc, so we need to include
that too.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Since Matrox MGA recipe is moved to common, include
the Matrox MGA varialbe to romley.conf.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Matrox MGA Xorg driver is being used by other meta-intel
BSPs. So move this to meta-intel/common/recipes-graphics.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
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>
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>
Update the SRCREV to include the
82580 Gigabit ethernet driver from meta branch
for the romley machine.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@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>
We want a failure to occur if the files specified in these statements
can't be found (e.g. when there is a misconfiguration), so use require
instead of include.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
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>
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 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>
This layer provides new BSP meta-romley.
This provides the support for Romley + Patsburg Chipset for Intel Systems.
Romley refers to the Intel Rosecity Board.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
