summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-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.
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
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.
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
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 \
To 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.
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
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 \
To 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.
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
-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 \
The 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
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 jasperforest
-image by adding the location of the meta-jasperforest layer to
-bblayers.conf e.g.:
+at the top-level of your yocto build tree, you can build a
+jasperforest image by adding the location of the meta-jasperforest
+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 \
To 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.
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
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 \
To 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.
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
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 \
To enable the sugarbay layer, add the sugarbay MACHINE to local.conf: