summaryrefslogtreecommitdiffstats
path: root/meta-emenlow
diff options
context:
space:
mode:
authorTom Zanussi <tom.zanussi@intel.com>2011-05-26 20:22:29 (GMT)
committerTom Zanussi <tom.zanussi@intel.com>2011-05-26 20:22:29 (GMT)
commitb0f4192e67e3140e41870b967977a2440a415c93 (patch)
treefd235b68fe5222177d42f3d8ebea760ea416dd79 /meta-emenlow
parentfc719f0cd6530ce15148b4aa274f1644b461b298 (diff)
downloadmeta-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')
-rw-r--r--meta-emenlow/README20
1 files changed, 12 insertions, 8 deletions
diff --git a/meta-emenlow/README b/meta-emenlow/README
index e724b13..6592a70 100644
--- a/meta-emenlow/README
+++ b/meta-emenlow/README
@@ -23,16 +23,11 @@ II. Booting the images in /binary
23I. Building the meta-emenlow BSP layer 23I. Building the meta-emenlow BSP layer
24======================================= 24=======================================
25 25
26The 'meta-intel' repository contains multiple branches, one
27corresponding to each major release starting with 'laverne' (0.90), in
28addition to the latest code which tracks the current master.
29
30In order to build an image with BSP support for a given release, you 26In order to build an image with BSP support for a given release, you
31need to check out the 'meta-intel' branch corresponding to the release 27need to download the corresponding BSP tarball from the 'Board Support
32you're building against e.g. to build for laverne (0.90), check out 28Package (BSP) Downloads' page of the Yocto Project website.
33the 'laverne' branch of both poky and 'meta-intel'.
34 29
35Having done that, and assuming you cloned the 'meta-intel' repository 30Having done that, and assuming you extracted the BSP tarball contents
36at the top-level of your yocto build tree, you can build an emenlow 31at the top-level of your yocto build tree, you can build an emenlow
37image by adding the location of the meta-emenlow layer to 32image by adding the location of the meta-emenlow layer to
38bblayers.conf e.g.: 33bblayers.conf e.g.:
@@ -52,6 +47,15 @@ At the end of a successful build, you should have a live image that
52you can boot from a USB flash drive (see instructions on how to do 47you can boot from a USB flash drive (see instructions on how to do
53that below, in the section 'Booting the images from /binary'). 48that below, in the section 'Booting the images from /binary').
54 49
50As an alternative to downloading the BSP tarball, you can also work
51directly from the meta-intel git repository. For each BSP in the
52'meta-intel' repository, there are multiple branches, one
53corresponding to each major release starting with 'laverne' (0.90), in
54addition to the latest code which tracks the current master. Instead
55of extracting a BSP tarball at the top level of your yocto build tree,
56you can equivalently check out the appropriate branch from the
57meta-intel repository at the same location.
58
55 59
56II. Booting the images in /binary 60II. Booting the images in /binary
57================================= 61=================================