diff options
author | Tom Zanussi <tom.zanussi@intel.com> | 2011-05-26 12:26:08 -0500 |
---|---|---|
committer | Tom Zanussi <tom.zanussi@intel.com> | 2011-05-26 12:26:08 -0500 |
commit | fc719f0cd6530ce15148b4aa274f1644b461b298 (patch) | |
tree | a8729686e7d399c5951f39a06207122f6db9b319 /meta-sugarbay/README | |
parent | f113449eb132df7c8a4c45ad8719ecc3ec84a6b5 (diff) | |
download | meta-intel-fc719f0cd6530ce15148b4aa274f1644b461b298.tar.gz |
meta-sugarbay: Change build instructions in README to use BSP tarball1.1_M1.rc21.1_M1
Change the build instructions to use BSP tarballs instead of git
clones. The git clone info remains as a mentioned alternative.
Fixes [YOCTO #1103].
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Diffstat (limited to 'meta-sugarbay/README')
-rw-r--r-- | meta-sugarbay/README | 21 |
1 files changed, 12 insertions, 9 deletions
diff --git a/meta-sugarbay/README b/meta-sugarbay/README index bcc46c23..78992052 100644 --- a/meta-sugarbay/README +++ b/meta-sugarbay/README | |||
@@ -17,17 +17,11 @@ III. Booting the images in /binary | |||
17 | I. Building the meta-sugarbay BSP layer | 17 | I. Building the meta-sugarbay BSP layer |
18 | ======================================= | 18 | ======================================= |
19 | 19 | ||
20 | For each BSP in the 'meta-intel' repository, there are multiple | ||
21 | branches, one corresponding to each major release starting with | ||
22 | 'laverne' (0.90), in addition to the latest code which tracks the | ||
23 | current master. | ||
24 | |||
25 | In order to build an image with BSP support for a given release, you | 20 | In order to build an image with BSP support for a given release, you |
26 | need to check out the 'meta-intel' branch corresponding to the release | 21 | need to download the corresponding BSP tarball from the 'Board Support |
27 | you're building against e.g. to build for laverne (0.90), check out | 22 | Package (BSP) Downloads' page of the Yocto Project website. |
28 | the 'laverne' branch of both poky and 'meta-intel'. | ||
29 | 23 | ||
30 | Having done that, and assuming you cloned the 'meta-intel' repository | 24 | Having done that, and assuming you extracted the BSP tarball contents |
31 | at the top-level of your yocto build tree, you can build a sugarbay | 25 | at the top-level of your yocto build tree, you can build a sugarbay |
32 | image by adding the location of the meta-sugarbay layer to | 26 | image by adding the location of the meta-sugarbay layer to |
33 | bblayers.conf e.g.: | 27 | bblayers.conf e.g.: |
@@ -47,6 +41,15 @@ At the end of a successful build, you should have a live image that | |||
47 | you can boot from a USB flash drive (see instructions on how to do | 41 | you can boot from a USB flash drive (see instructions on how to do |
48 | that below, in the section 'Booting the images from /binary'). | 42 | that below, in the section 'Booting the images from /binary'). |
49 | 43 | ||
44 | As an alternative to downloading the BSP tarball, you can also work | ||
45 | directly from the meta-intel git repository. For each BSP in the | ||
46 | 'meta-intel' repository, there are multiple branches, one | ||
47 | corresponding to each major release starting with 'laverne' (0.90), in | ||
48 | addition to the latest code which tracks the current master. Instead | ||
49 | of extracting a BSP tarball at the top level of your yocto build tree, | ||
50 | you can equivalently check out the appropriate branch from the | ||
51 | meta-intel repository at the same location. | ||
52 | |||
50 | 53 | ||
51 | II. Booting the images in /binary | 54 | II. Booting the images in /binary |
52 | ================================= | 55 | ================================= |