aboutsummaryrefslogtreecommitdiffstats
path: root/meta-crownbay/README
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 /meta-crownbay/README
parent0d39ed8727fca64e0a3ea428c4977d8a1a9ad2c8 (diff)
downloadmeta-intel-f01a136a0db28abe1267a290a454d6029fb3d989.tar.gz
meta-intel-f01a136a0db28abe1267a290a454d6029fb3d989.tar.bz2
meta-intel-f01a136a0db28abe1267a290a454d6029fb3d989.zip
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>
Diffstat (limited to 'meta-crownbay/README')
-rw-r--r--meta-crownbay/README4
1 files changed, 3 insertions, 1 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.
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
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 \
The meta-crownbay layer contains support for two different machine