meta-intel: update READMEs with new layer info

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 commit is contained in:
Tom Zanussi 2011-11-19 22:06:53 -06:00
parent 0d39ed8727
commit f01a136a0d
7 changed files with 24 additions and 9 deletions

View File

@ -26,8 +26,10 @@ Package (BSP) Downloads' page of the Yocto Project website.
Having done that, and assuming you extracted the BSP tarball contents Having done that, and assuming you extracted the BSP tarball contents
at the top-level of your yocto build tree, you can build a crownbay at the top-level of your yocto build tree, you can build a crownbay
image by adding the location of the meta-crownbay layer to image by adding the location of the meta-crownbay layer to
bblayers.conf e.g.: bblayers.conf, along with the meta-intel layer itself (to access
common metadata shared between BSPs) e.g.:
yocto/meta-intel \
yocto/meta-intel/meta-crownbay \ yocto/meta-intel/meta-crownbay \
The meta-crownbay layer contains support for two different machine The meta-crownbay layer contains support for two different machine

View File

@ -30,8 +30,10 @@ Package (BSP) Downloads' page of the Yocto Project website.
Having done that, and assuming you extracted the BSP tarball contents Having done that, and assuming you extracted the BSP tarball contents
at the top-level of your yocto build tree, you can build an emenlow at the top-level of your yocto build tree, you can build an emenlow
image by adding the location of the meta-emenlow layer to image by adding the location of the meta-emenlow layer to
bblayers.conf e.g.: bblayers.conf, along with the meta-intel layer itself (to access
common metadata shared between BSPs) e.g.:
yocto/meta-intel \
yocto/meta-intel/meta-emenlow \ yocto/meta-intel/meta-emenlow \
To enable the emenlow layer, add the emenlow MACHINE to local.conf: To enable the emenlow layer, add the emenlow MACHINE to local.conf:

View File

@ -20,8 +20,10 @@ Package (BSP) Downloads' page of the Yocto Project website.
Having done that, and assuming you extracted the BSP tarball contents Having done that, and assuming you extracted the BSP tarball contents
at the top-level of your yocto build tree, you can build a fishriver at the top-level of your yocto build tree, you can build a fishriver
image by adding the location of the meta-fishriver layer to image by adding the location of the meta-fishriver layer to
bblayers.conf e.g.: bblayers.conf, along with the meta-intel layer itself (to access
common metadata shared between BSPs) e.g.:
yocto/meta-intel \
yocto/meta-intel/meta-fishriver \ yocto/meta-intel/meta-fishriver \
To enable the fishriver layer, add the fishriver MACHINE to local.conf: To enable the fishriver layer, add the fishriver MACHINE to local.conf:

View File

@ -28,8 +28,11 @@ Package (BSP) Downloads' page of the Yocto Project website.
Having done that, and assuming you extracted the BSP tarball contents Having done that, and assuming you extracted the BSP tarball contents
at the top-level of your yocto build tree, you can build an fri2 image at the top-level of your yocto build tree, you can build an fri2 image
by adding the location of the meta-fri2 layer to bblayers.conf e.g.: by adding the location of the meta-fri2 layer to bblayers.conf, along
with the meta-intel layer itself (to access common metadata shared
between BSPs) e.g.:
yocto/meta-intel \
yocto/meta-intel/meta-fri2 \ yocto/meta-intel/meta-fri2 \
The meta-fri2 layer contains support for two different machine The meta-fri2 layer contains support for two different machine

View File

@ -23,10 +23,12 @@ need to download the corresponding BSP tarball from the 'Board Support
Package (BSP) Downloads' page of the Yocto Project website. Package (BSP) Downloads' page of the Yocto Project website.
Having done that, and assuming you extracted the BSP tarball contents Having done that, and assuming you extracted the BSP tarball contents
at the top-level of your yocto build tree, you can build a jasperforest at the top-level of your yocto build tree, you can build a
image by adding the location of the meta-jasperforest layer to jasperforest image by adding the location of the meta-jasperforest
bblayers.conf e.g.: layer to bblayers.conf, along with the meta-intel layer itself (to
access common metadata shared between BSPs) e.g.:
yocto/meta-intel \
yocto/meta-intel/meta-jasperforest \ yocto/meta-intel/meta-jasperforest \
To enable the jasperforest layer, add the jasperforest MACHINE to local.conf: To enable the jasperforest layer, add the jasperforest MACHINE to local.conf:

View File

@ -22,8 +22,10 @@ Package (BSP) Downloads' page of the Yocto Project website.
Having done that, and assuming you extracted the BSP tarball contents Having done that, and assuming you extracted the BSP tarball contents
at the top-level of your yocto build tree, you can build a romley at the top-level of your yocto build tree, you can build a romley
image by adding the location of the meta-romley layer to image by adding the location of the meta-romley layer to
bblayers.conf e.g.: bblayers.conf, along with the meta-intel layer itself (to access
common metadata shared between BSPs) e.g.:
yocto/meta-intel \
yocto/meta-intel/meta-romley \ yocto/meta-intel/meta-romley \
To enable the romley layer, add the romley MACHINE to local.conf: To enable the romley layer, add the romley MACHINE to local.conf:

View File

@ -23,8 +23,10 @@ Package (BSP) Downloads' page of the Yocto Project website.
Having done that, and assuming you extracted the BSP tarball contents Having done that, and assuming you extracted the BSP tarball contents
at the top-level of your yocto build tree, you can build a sugarbay at the top-level of your yocto build tree, you can build a sugarbay
image by adding the location of the meta-sugarbay layer to image by adding the location of the meta-sugarbay layer to
bblayers.conf e.g.: bblayers.conf, along with the meta-intel layer itself (to access
common metadata shared between BSPs) e.g.:
yocto/meta-intel \
yocto/meta-intel/meta-sugarbay \ yocto/meta-intel/meta-sugarbay \
To enable the sugarbay layer, add the sugarbay MACHINE to local.conf: To enable the sugarbay layer, add the sugarbay MACHINE to local.conf: