diff options
-rw-r--r-- | meta-crownbay/README | 21 | ||||
-rw-r--r-- | meta-emenlow/README | 20 | ||||
-rw-r--r-- | meta-fishriver/README | 21 | ||||
-rw-r--r-- | meta-jasperforest/README | 21 |
4 files changed, 48 insertions, 35 deletions
diff --git a/meta-crownbay/README b/meta-crownbay/README index 11770246..bb1e0c3f 100644 --- a/meta-crownbay/README +++ b/meta-crownbay/README | |||
@@ -19,17 +19,11 @@ III. Booting the images in /binary | |||
19 | I. Building the meta-crownbay BSP layer | 19 | I. Building the meta-crownbay BSP layer |
20 | ======================================= | 20 | ======================================= |
21 | 21 | ||
22 | For each BSP in the 'meta-intel' repository, there are multiple | ||
23 | branches, one corresponding to each major release starting with | ||
24 | 'laverne' (0.90), in addition to the latest code which tracks the | ||
25 | current master. | ||
26 | |||
27 | In order to build an image with BSP support for a given release, you | 22 | In order to build an image with BSP support for a given release, you |
28 | need to check out the 'meta-intel' branch corresponding to the release | 23 | need to download the corresponding BSP tarball from the 'Board Support |
29 | you're building against e.g. to build for bernard (1.0), check out | 24 | Package (BSP) Downloads' page of the Yocto Project website. |
30 | the 'bernard' branch of both poky and 'meta-intel'. | ||
31 | 25 | ||
32 | Having done that, and assuming you cloned the 'meta-intel' repository | 26 | Having done that, and assuming you extracted the BSP tarball contents |
33 | 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 |
34 | image by adding the location of the meta-crownbay layer to | 28 | image by adding the location of the meta-crownbay layer to |
35 | bblayers.conf e.g.: | 29 | bblayers.conf e.g.: |
@@ -61,6 +55,15 @@ At the end of a successful build, you should have a live image that | |||
61 | you can boot from a USB flash drive (see instructions on how to do | 55 | you can boot from a USB flash drive (see instructions on how to do |
62 | that below, in the section 'Booting the images from /binary'). | 56 | that below, in the section 'Booting the images from /binary'). |
63 | 57 | ||
58 | As an alternative to downloading the BSP tarball, you can also work | ||
59 | directly from the meta-intel git repository. For each BSP in the | ||
60 | 'meta-intel' repository, there are multiple branches, one | ||
61 | corresponding to each major release starting with 'laverne' (0.90), in | ||
62 | addition to the latest code which tracks the current master. Instead | ||
63 | of extracting a BSP tarball at the top level of your yocto build tree, | ||
64 | you can equivalently check out the appropriate branch from the | ||
65 | meta-intel repository at the same location. | ||
66 | |||
64 | 67 | ||
65 | II. Special notes for building the meta-crownbay BSP layer | 68 | II. Special notes for building the meta-crownbay BSP layer |
66 | ========================================================== | 69 | ========================================================== |
diff --git a/meta-emenlow/README b/meta-emenlow/README index e724b135..6592a705 100644 --- a/meta-emenlow/README +++ b/meta-emenlow/README | |||
@@ -23,16 +23,11 @@ II. Booting the images in /binary | |||
23 | I. Building the meta-emenlow BSP layer | 23 | I. Building the meta-emenlow BSP layer |
24 | ======================================= | 24 | ======================================= |
25 | 25 | ||
26 | The 'meta-intel' repository contains multiple branches, one | ||
27 | corresponding to each major release starting with 'laverne' (0.90), in | ||
28 | addition to the latest code which tracks the current master. | ||
29 | |||
30 | In order to build an image with BSP support for a given release, you | 26 | In order to build an image with BSP support for a given release, you |
31 | need to check out the 'meta-intel' branch corresponding to the release | 27 | need to download the corresponding BSP tarball from the 'Board Support |
32 | you're building against e.g. to build for laverne (0.90), check out | 28 | Package (BSP) Downloads' page of the Yocto Project website. |
33 | the 'laverne' branch of both poky and 'meta-intel'. | ||
34 | 29 | ||
35 | Having done that, and assuming you cloned the 'meta-intel' repository | 30 | Having done that, and assuming you extracted the BSP tarball contents |
36 | 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 |
37 | image by adding the location of the meta-emenlow layer to | 32 | image by adding the location of the meta-emenlow layer to |
38 | bblayers.conf e.g.: | 33 | bblayers.conf e.g.: |
@@ -52,6 +47,15 @@ At the end of a successful build, you should have a live image that | |||
52 | you can boot from a USB flash drive (see instructions on how to do | 47 | you can boot from a USB flash drive (see instructions on how to do |
53 | that below, in the section 'Booting the images from /binary'). | 48 | that below, in the section 'Booting the images from /binary'). |
54 | 49 | ||
50 | As an alternative to downloading the BSP tarball, you can also work | ||
51 | directly from the meta-intel git repository. For each BSP in the | ||
52 | 'meta-intel' repository, there are multiple branches, one | ||
53 | corresponding to each major release starting with 'laverne' (0.90), in | ||
54 | addition to the latest code which tracks the current master. Instead | ||
55 | of extracting a BSP tarball at the top level of your yocto build tree, | ||
56 | you can equivalently check out the appropriate branch from the | ||
57 | meta-intel repository at the same location. | ||
58 | |||
55 | 59 | ||
56 | II. Booting the images in /binary | 60 | II. Booting the images in /binary |
57 | ================================= | 61 | ================================= |
diff --git a/meta-fishriver/README b/meta-fishriver/README index 57b49264..1ffbbf1a 100644 --- a/meta-fishriver/README +++ b/meta-fishriver/README | |||
@@ -27,17 +27,11 @@ config changes for: | |||
27 | II. Building the meta-fishriver BSP layer | 27 | II. Building the meta-fishriver BSP layer |
28 | ========================================= | 28 | ========================================= |
29 | 29 | ||
30 | For each BSP in the 'meta-intel' repository, there are multiple | ||
31 | branches, one corresponding to each major release starting with | ||
32 | 'laverne' (0.90), in addition to the latest code which tracks the | ||
33 | current master. | ||
34 | |||
35 | In order to build an image with BSP support for a given release, you | 30 | In order to build an image with BSP support for a given release, you |
36 | need to check out the 'meta-intel' branch corresponding to the release | 31 | need to download the corresponding BSP tarball from the 'Board Support |
37 | you're building against e.g. to build for laverne (0.90), check out | 32 | Package (BSP) Downloads' page of the Yocto Project website. |
38 | the 'laverne' branch of both poky and 'meta-intel'. | ||
39 | 33 | ||
40 | Having done that, and assuming you cloned the 'meta-intel' repository | 34 | Having done that, and assuming you extracted the BSP tarball contents |
41 | at the top-level of your yocto build tree, you can build a fishriver | 35 | at the top-level of your yocto build tree, you can build a fishriver |
42 | image by adding the location of the meta-fishriver layer to | 36 | image by adding the location of the meta-fishriver layer to |
43 | bblayers.conf e.g.: | 37 | bblayers.conf e.g.: |
@@ -57,6 +51,15 @@ At the end of a successful build, you should have a live image that | |||
57 | you can boot from a USB flash drive (see instructions on how to do | 51 | you can boot from a USB flash drive (see instructions on how to do |
58 | that below, in the section 'Booting the images from /binary'). | 52 | that below, in the section 'Booting the images from /binary'). |
59 | 53 | ||
54 | As an alternative to downloading the BSP tarball, you can also work | ||
55 | directly from the meta-intel git repository. For each BSP in the | ||
56 | 'meta-intel' repository, there are multiple branches, one | ||
57 | corresponding to each major release starting with 'laverne' (0.90), in | ||
58 | addition to the latest code which tracks the current master. Instead | ||
59 | of extracting a BSP tarball at the top level of your yocto build tree, | ||
60 | you can equivalently check out the appropriate branch from the | ||
61 | meta-intel repository at the same location. | ||
62 | |||
60 | 63 | ||
61 | III. Booting the images in /binary | 64 | III. Booting the images in /binary |
62 | ================================== | 65 | ================================== |
diff --git a/meta-jasperforest/README b/meta-jasperforest/README index ab7246d9..6421d06a 100644 --- a/meta-jasperforest/README +++ b/meta-jasperforest/README | |||
@@ -18,17 +18,11 @@ Table of Contents | |||
18 | I. Building the meta-jasperforest BSP layer | 18 | I. Building the meta-jasperforest BSP layer |
19 | ======================================= | 19 | ======================================= |
20 | 20 | ||
21 | For each BSP in the 'meta-intel' repository, there are multiple | ||
22 | branches, one corresponding to each major release starting with | ||
23 | 'laverne' (0.90), in addition to the latest code which tracks the | ||
24 | current master. | ||
25 | |||
26 | In order to build an image with BSP support for a given release, you | 21 | In order to build an image with BSP support for a given release, you |
27 | need to check out the 'meta-intel' branch corresponding to the release | 22 | need to download the corresponding BSP tarball from the 'Board Support |
28 | you're building against e.g. to build for laverne (0.90), check out | 23 | Package (BSP) Downloads' page of the Yocto Project website. |
29 | the 'laverne' branch of both poky and 'meta-intel'. | ||
30 | 24 | ||
31 | Having done that, and assuming you cloned the 'meta-intel' repository | 25 | Having done that, and assuming you extracted the BSP tarball contents |
32 | 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 jasperforest |
33 | image by adding the location of the meta-jasperforest layer to | 27 | image by adding the location of the meta-jasperforest layer to |
34 | bblayers.conf e.g.: | 28 | bblayers.conf e.g.: |
@@ -48,6 +42,15 @@ At the end of a successful build, you should have a live image that | |||
48 | you can boot from a USB flash drive (see instructions on how to do | 42 | you can boot from a USB flash drive (see instructions on how to do |
49 | that below, in the section 'Booting the images from /binary'). | 43 | that below, in the section 'Booting the images from /binary'). |
50 | 44 | ||
45 | As an alternative to downloading the BSP tarball, you can also work | ||
46 | directly from the meta-intel git repository. For each BSP in the | ||
47 | 'meta-intel' repository, there are multiple branches, one | ||
48 | corresponding to each major release starting with 'laverne' (0.90), in | ||
49 | addition to the latest code which tracks the current master. Instead | ||
50 | of extracting a BSP tarball at the top level of your yocto build tree, | ||
51 | you can equivalently check out the appropriate branch from the | ||
52 | meta-intel repository at the same location. | ||
53 | |||
51 | 54 | ||
52 | II. Booting the images in /binary | 55 | II. Booting the images in /binary |
53 | ================================= | 56 | ================================= |