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