diff options
-rw-r--r-- | meta-crownbay/README | 4 | ||||
-rw-r--r-- | meta-emenlow/README | 4 | ||||
-rw-r--r-- | meta-fishriver/README | 4 | ||||
-rw-r--r-- | meta-fri2/README | 5 | ||||
-rw-r--r-- | meta-jasperforest/README | 8 | ||||
-rw-r--r-- | meta-romley/README | 4 | ||||
-rw-r--r-- | meta-sugarbay/README | 4 |
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. | |||
26 | Having done that, and assuming you extracted the BSP tarball contents | 26 | Having done that, and assuming you extracted the BSP tarball contents |
27 | at the top-level of your yocto build tree, you can build a crownbay | 27 | at the top-level of your yocto build tree, you can build a crownbay |
28 | image by adding the location of the meta-crownbay layer to | 28 | image by adding the location of the meta-crownbay layer to |
29 | bblayers.conf e.g.: | 29 | bblayers.conf, along with the meta-intel layer itself (to access |
30 | common 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 | ||
33 | The meta-crownbay layer contains support for two different machine | 35 | 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. | |||
30 | Having done that, and assuming you extracted the BSP tarball contents | 30 | Having done that, and assuming you extracted the BSP tarball contents |
31 | at the top-level of your yocto build tree, you can build an emenlow | 31 | at the top-level of your yocto build tree, you can build an emenlow |
32 | image by adding the location of the meta-emenlow layer to | 32 | image by adding the location of the meta-emenlow layer to |
33 | bblayers.conf e.g.: | 33 | bblayers.conf, along with the meta-intel layer itself (to access |
34 | common 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 | ||
37 | To enable the emenlow layer, add the emenlow MACHINE to local.conf: | 39 | 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. | |||
20 | Having done that, and assuming you extracted the BSP tarball contents | 20 | Having done that, and assuming you extracted the BSP tarball contents |
21 | at the top-level of your yocto build tree, you can build a fishriver | 21 | at the top-level of your yocto build tree, you can build a fishriver |
22 | image by adding the location of the meta-fishriver layer to | 22 | image by adding the location of the meta-fishriver layer to |
23 | bblayers.conf e.g.: | 23 | bblayers.conf, along with the meta-intel layer itself (to access |
24 | common 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 | ||
27 | To enable the fishriver layer, add the fishriver MACHINE to local.conf: | 29 | 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. | |||
28 | 28 | ||
29 | Having done that, and assuming you extracted the BSP tarball contents | 29 | Having done that, and assuming you extracted the BSP tarball contents |
30 | at the top-level of your yocto build tree, you can build an fri2 image | 30 | at the top-level of your yocto build tree, you can build an fri2 image |
31 | by adding the location of the meta-fri2 layer to bblayers.conf e.g.: | 31 | by adding the location of the meta-fri2 layer to bblayers.conf, along |
32 | with the meta-intel layer itself (to access common metadata shared | ||
33 | between BSPs) e.g.: | ||
32 | 34 | ||
35 | yocto/meta-intel \ | ||
33 | yocto/meta-intel/meta-fri2 \ | 36 | yocto/meta-intel/meta-fri2 \ |
34 | 37 | ||
35 | The meta-fri2 layer contains support for two different machine | 38 | 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 | |||
23 | Package (BSP) Downloads' page of the Yocto Project website. | 23 | Package (BSP) Downloads' page of the Yocto Project website. |
24 | 24 | ||
25 | Having done that, and assuming you extracted the BSP tarball contents | 25 | Having done that, and assuming you extracted the BSP tarball contents |
26 | at the top-level of your yocto build tree, you can build a jasperforest | 26 | at the top-level of your yocto build tree, you can build a |
27 | image by adding the location of the meta-jasperforest layer to | 27 | jasperforest image by adding the location of the meta-jasperforest |
28 | bblayers.conf e.g.: | 28 | layer to bblayers.conf, along with the meta-intel layer itself (to |
29 | access 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 | ||
32 | To enable the jasperforest layer, add the jasperforest MACHINE to local.conf: | 34 | 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. | |||
22 | Having done that, and assuming you extracted the BSP tarball contents | 22 | Having done that, and assuming you extracted the BSP tarball contents |
23 | at the top-level of your yocto build tree, you can build a romley | 23 | at the top-level of your yocto build tree, you can build a romley |
24 | image by adding the location of the meta-romley layer to | 24 | image by adding the location of the meta-romley layer to |
25 | bblayers.conf e.g.: | 25 | bblayers.conf, along with the meta-intel layer itself (to access |
26 | common 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 | ||
29 | To enable the romley layer, add the romley MACHINE to local.conf: | 31 | 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. | |||
23 | Having done that, and assuming you extracted the BSP tarball contents | 23 | Having done that, and assuming you extracted the BSP tarball contents |
24 | at the top-level of your yocto build tree, you can build a sugarbay | 24 | at the top-level of your yocto build tree, you can build a sugarbay |
25 | image by adding the location of the meta-sugarbay layer to | 25 | image by adding the location of the meta-sugarbay layer to |
26 | bblayers.conf e.g.: | 26 | bblayers.conf, along with the meta-intel layer itself (to access |
27 | common 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 | ||
30 | To enable the sugarbay layer, add the sugarbay MACHINE to local.conf: | 32 | To enable the sugarbay layer, add the sugarbay MACHINE to local.conf: |