diff options
| author | Tom Zanussi <tom.zanussi@intel.com> | 2011-05-26 15:22:29 -0500 |
|---|---|---|
| committer | Tom Zanussi <tom.zanussi@intel.com> | 2011-05-26 15:22:29 -0500 |
| commit | b0f4192e67e3140e41870b967977a2440a415c93 (patch) | |
| tree | fd235b68fe5222177d42f3d8ebea760ea416dd79 /meta-emenlow/README | |
| 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-emenlow/README')
| -rw-r--r-- | meta-emenlow/README | 20 |
1 files changed, 12 insertions, 8 deletions
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 | ================================= |
