summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTom Zanussi <tom.zanussi@intel.com>2011-11-19 22:06:53 -0600
committerTom Zanussi <tom.zanussi@intel.com>2011-11-21 09:30:00 -0600
commitf01a136a0db28abe1267a290a454d6029fb3d989 (patch)
tree1ce183d5fccf8b5b957cba6490f262a2625af05b
parent0d39ed8727fca64e0a3ea428c4977d8a1a9ad2c8 (diff)
downloadmeta-intel-f01a136a0db28abe1267a290a454d6029fb3d989.tar.gz
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>
-rw-r--r--meta-crownbay/README4
-rw-r--r--meta-emenlow/README4
-rw-r--r--meta-fishriver/README4
-rw-r--r--meta-fri2/README5
-rw-r--r--meta-jasperforest/README8
-rw-r--r--meta-romley/README4
-rw-r--r--meta-sugarbay/README4
7 files changed, 24 insertions, 9 deletions
diff --git a/meta-crownbay/README b/meta-crownbay/README
index de9f1f1c..7d96bc22 100644
--- a/meta-crownbay/README
+++ b/meta-crownbay/README
@@ -26,8 +26,10 @@ Package (BSP) Downloads' page of the Yocto Project website.
26Having done that, and assuming you extracted the BSP tarball contents 26Having done that, and assuming you extracted the BSP tarball contents
27at the top-level of your yocto build tree, you can build a crownbay 27at the top-level of your yocto build tree, you can build a crownbay
28image by adding the location of the meta-crownbay layer to 28image by adding the location of the meta-crownbay layer to
29bblayers.conf e.g.: 29bblayers.conf, along with the meta-intel layer itself (to access
30common metadata shared between BSPs) e.g.:
30 31
32 yocto/meta-intel \
31 yocto/meta-intel/meta-crownbay \ 33 yocto/meta-intel/meta-crownbay \
32 34
33The meta-crownbay layer contains support for two different machine 35The meta-crownbay layer contains support for two different machine
diff --git a/meta-emenlow/README b/meta-emenlow/README
index fc3317e3..d802bfb4 100644
--- a/meta-emenlow/README
+++ b/meta-emenlow/README
@@ -30,8 +30,10 @@ Package (BSP) Downloads' page of the Yocto Project website.
30Having done that, and assuming you extracted the BSP tarball contents 30Having done that, and assuming you extracted the BSP tarball contents
31at the top-level of your yocto build tree, you can build an emenlow 31at the top-level of your yocto build tree, you can build an emenlow
32image by adding the location of the meta-emenlow layer to 32image by adding the location of the meta-emenlow layer to
33bblayers.conf e.g.: 33bblayers.conf, along with the meta-intel layer itself (to access
34common metadata shared between BSPs) e.g.:
34 35
36 yocto/meta-intel \
35 yocto/meta-intel/meta-emenlow \ 37 yocto/meta-intel/meta-emenlow \
36 38
37To enable the emenlow layer, add the emenlow MACHINE to local.conf: 39To enable the emenlow layer, add the emenlow MACHINE to local.conf:
diff --git a/meta-fishriver/README b/meta-fishriver/README
index b76056c5..6425432e 100644
--- a/meta-fishriver/README
+++ b/meta-fishriver/README
@@ -20,8 +20,10 @@ Package (BSP) Downloads' page of the Yocto Project website.
20Having done that, and assuming you extracted the BSP tarball contents 20Having done that, and assuming you extracted the BSP tarball contents
21at the top-level of your yocto build tree, you can build a fishriver 21at the top-level of your yocto build tree, you can build a fishriver
22image by adding the location of the meta-fishriver layer to 22image by adding the location of the meta-fishriver layer to
23bblayers.conf e.g.: 23bblayers.conf, along with the meta-intel layer itself (to access
24common metadata shared between BSPs) e.g.:
24 25
26 yocto/meta-intel \
25 yocto/meta-intel/meta-fishriver \ 27 yocto/meta-intel/meta-fishriver \
26 28
27To enable the fishriver layer, add the fishriver MACHINE to local.conf: 29To enable the fishriver layer, add the fishriver MACHINE to local.conf:
diff --git a/meta-fri2/README b/meta-fri2/README
index 4dc135b3..12b0b37d 100644
--- a/meta-fri2/README
+++ b/meta-fri2/README
@@ -28,8 +28,11 @@ Package (BSP) Downloads' page of the Yocto Project website.
28 28
29Having done that, and assuming you extracted the BSP tarball contents 29Having done that, and assuming you extracted the BSP tarball contents
30at the top-level of your yocto build tree, you can build an fri2 image 30at the top-level of your yocto build tree, you can build an fri2 image
31by adding the location of the meta-fri2 layer to bblayers.conf e.g.: 31by adding the location of the meta-fri2 layer to bblayers.conf, along
32with the meta-intel layer itself (to access common metadata shared
33between BSPs) e.g.:
32 34
35 yocto/meta-intel \
33 yocto/meta-intel/meta-fri2 \ 36 yocto/meta-intel/meta-fri2 \
34 37
35The meta-fri2 layer contains support for two different machine 38The meta-fri2 layer contains support for two different machine
diff --git a/meta-jasperforest/README b/meta-jasperforest/README
index 7652da09..a464a114 100644
--- a/meta-jasperforest/README
+++ b/meta-jasperforest/README
@@ -23,10 +23,12 @@ need to download the corresponding BSP tarball from the 'Board Support
23Package (BSP) Downloads' page of the Yocto Project website. 23Package (BSP) Downloads' page of the Yocto Project website.
24 24
25Having done that, and assuming you extracted the BSP tarball contents 25Having done that, and assuming you extracted the BSP tarball contents
26at the top-level of your yocto build tree, you can build a jasperforest 26at the top-level of your yocto build tree, you can build a
27image by adding the location of the meta-jasperforest layer to 27jasperforest image by adding the location of the meta-jasperforest
28bblayers.conf e.g.: 28layer to bblayers.conf, along with the meta-intel layer itself (to
29access common metadata shared between BSPs) e.g.:
29 30
31 yocto/meta-intel \
30 yocto/meta-intel/meta-jasperforest \ 32 yocto/meta-intel/meta-jasperforest \
31 33
32To enable the jasperforest layer, add the jasperforest MACHINE to local.conf: 34To enable the jasperforest layer, add the jasperforest MACHINE to local.conf:
diff --git a/meta-romley/README b/meta-romley/README
index d242534d..6c13ea69 100644
--- a/meta-romley/README
+++ b/meta-romley/README
@@ -22,8 +22,10 @@ Package (BSP) Downloads' page of the Yocto Project website.
22Having done that, and assuming you extracted the BSP tarball contents 22Having done that, and assuming you extracted the BSP tarball contents
23at the top-level of your yocto build tree, you can build a romley 23at the top-level of your yocto build tree, you can build a romley
24image by adding the location of the meta-romley layer to 24image by adding the location of the meta-romley layer to
25bblayers.conf e.g.: 25bblayers.conf, along with the meta-intel layer itself (to access
26common metadata shared between BSPs) e.g.:
26 27
28 yocto/meta-intel \
27 yocto/meta-intel/meta-romley \ 29 yocto/meta-intel/meta-romley \
28 30
29To enable the romley layer, add the romley MACHINE to local.conf: 31To enable the romley layer, add the romley MACHINE to local.conf:
diff --git a/meta-sugarbay/README b/meta-sugarbay/README
index 2d72f8a6..72b1faff 100644
--- a/meta-sugarbay/README
+++ b/meta-sugarbay/README
@@ -23,8 +23,10 @@ Package (BSP) Downloads' page of the Yocto Project website.
23Having done that, and assuming you extracted the BSP tarball contents 23Having done that, and assuming you extracted the BSP tarball contents
24at the top-level of your yocto build tree, you can build a sugarbay 24at the top-level of your yocto build tree, you can build a sugarbay
25image by adding the location of the meta-sugarbay layer to 25image by adding the location of the meta-sugarbay layer to
26bblayers.conf e.g.: 26bblayers.conf, along with the meta-intel layer itself (to access
27common metadata shared between BSPs) e.g.:
27 28
29 yocto/meta-intel \
28 yocto/meta-intel/meta-sugarbay \ 30 yocto/meta-intel/meta-sugarbay \
29 31
30To enable the sugarbay layer, add the sugarbay MACHINE to local.conf: 32To enable the sugarbay layer, add the sugarbay MACHINE to local.conf: