diff options
author | Tom Zanussi <tom.zanussi@intel.com> | 2011-05-26 20:22:29 (GMT) |
---|---|---|
committer | Tom Zanussi <tom.zanussi@intel.com> | 2011-05-26 20:22:29 (GMT) |
commit | b0f4192e67e3140e41870b967977a2440a415c93 (patch) | |
tree | fd235b68fe5222177d42f3d8ebea760ea416dd79 /meta-jasperforest | |
parent | fc719f0cd6530ce15148b4aa274f1644b461b298 (diff) | |
download | meta-intel-b0f4192e67e3140e41870b967977a2440a415c93.tar.gz |
meta-intel: Change build instructions in README to use BSP tarball
Change the build instructions to use BSP tarballs instead of git
clones. The git clone info remains as a mentioned alternative.
The original bug report was for Sugar Bay, but the others had the same
problem - this fixes those up.
Fixes [YOCTO #1103].
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Diffstat (limited to 'meta-jasperforest')
-rw-r--r-- | meta-jasperforest/README | 21 |
1 files changed, 12 insertions, 9 deletions
diff --git a/meta-jasperforest/README b/meta-jasperforest/README index ab7246d..6421d06 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 | ================================= |