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 I. Building the meta-crownbay BSP layer ======================================= -For each BSP in the 'meta-intel' repository, there are multiple -branches, one corresponding to each major release starting with -'laverne' (0.90), in addition to the latest code which tracks the -current master. - In order to build an image with BSP support for a given release, you -need to check out the 'meta-intel' branch corresponding to the release -you're building against e.g. to build for bernard (1.0), check out -the 'bernard' branch of both poky and 'meta-intel'. +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 cloned the 'meta-intel' repository +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.: @@ -61,6 +55,15 @@ At the end of a successful build, you should have a live image that you can boot from a USB flash drive (see instructions on how to do that below, in the section 'Booting the images from /binary'). +As an alternative to downloading the BSP tarball, you can also work +directly from the meta-intel git repository. For each BSP in the +'meta-intel' repository, there are multiple branches, one +corresponding to each major release starting with 'laverne' (0.90), in +addition to the latest code which tracks the current master. Instead +of extracting a BSP tarball at the top level of your yocto build tree, +you can equivalently check out the appropriate branch from the +meta-intel repository at the same location. + II. Special notes for building the meta-crownbay BSP layer ========================================================== 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 I. Building the meta-emenlow BSP layer ======================================= -The 'meta-intel' repository contains multiple branches, one -corresponding to each major release starting with 'laverne' (0.90), in -addition to the latest code which tracks the current master. - In order to build an image with BSP support for a given release, you -need to check out the 'meta-intel' branch corresponding to the release -you're building against e.g. to build for laverne (0.90), check out -the 'laverne' branch of both poky and 'meta-intel'. +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 cloned the 'meta-intel' repository +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.: @@ -52,6 +47,15 @@ At the end of a successful build, you should have a live image that you can boot from a USB flash drive (see instructions on how to do that below, in the section 'Booting the images from /binary'). +As an alternative to downloading the BSP tarball, you can also work +directly from the meta-intel git repository. For each BSP in the +'meta-intel' repository, there are multiple branches, one +corresponding to each major release starting with 'laverne' (0.90), in +addition to the latest code which tracks the current master. Instead +of extracting a BSP tarball at the top level of your yocto build tree, +you can equivalently check out the appropriate branch from the +meta-intel repository at the same location. + II. Booting the images in /binary ================================= 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: II. Building the meta-fishriver BSP layer ========================================= -For each BSP in the 'meta-intel' repository, there are multiple -branches, one corresponding to each major release starting with -'laverne' (0.90), in addition to the latest code which tracks the -current master. - In order to build an image with BSP support for a given release, you -need to check out the 'meta-intel' branch corresponding to the release -you're building against e.g. to build for laverne (0.90), check out -the 'laverne' branch of both poky and 'meta-intel'. +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 cloned the 'meta-intel' repository +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.: @@ -57,6 +51,15 @@ At the end of a successful build, you should have a live image that you can boot from a USB flash drive (see instructions on how to do that below, in the section 'Booting the images from /binary'). +As an alternative to downloading the BSP tarball, you can also work +directly from the meta-intel git repository. For each BSP in the +'meta-intel' repository, there are multiple branches, one +corresponding to each major release starting with 'laverne' (0.90), in +addition to the latest code which tracks the current master. Instead +of extracting a BSP tarball at the top level of your yocto build tree, +you can equivalently check out the appropriate branch from the +meta-intel repository at the same location. + III. Booting the images in /binary ================================== 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 I. Building the meta-jasperforest BSP layer ======================================= -For each BSP in the 'meta-intel' repository, there are multiple -branches, one corresponding to each major release starting with -'laverne' (0.90), in addition to the latest code which tracks the -current master. - In order to build an image with BSP support for a given release, you -need to check out the 'meta-intel' branch corresponding to the release -you're building against e.g. to build for laverne (0.90), check out -the 'laverne' branch of both poky and 'meta-intel'. +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 cloned the 'meta-intel' repository +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.: @@ -48,6 +42,15 @@ At the end of a successful build, you should have a live image that you can boot from a USB flash drive (see instructions on how to do that below, in the section 'Booting the images from /binary'). +As an alternative to downloading the BSP tarball, you can also work +directly from the meta-intel git repository. For each BSP in the +'meta-intel' repository, there are multiple branches, one +corresponding to each major release starting with 'laverne' (0.90), in +addition to the latest code which tracks the current master. Instead +of extracting a BSP tarball at the top level of your yocto build tree, +you can equivalently check out the appropriate branch from the +meta-intel repository at the same location. + II. Booting the images in /binary ================================= |