summaryrefslogtreecommitdiffstats
path: root/meta-fishriver
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-fishriver
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-fishriver')
-rw-r--r--meta-fishriver/README21
1 files changed, 12 insertions, 9 deletions
diff --git a/meta-fishriver/README b/meta-fishriver/README
index 57b4926..1ffbbf1 100644
--- a/meta-fishriver/README
+++ b/meta-fishriver/README
@@ -27,17 +27,11 @@ config changes for:
27II. Building the meta-fishriver BSP layer 27II. Building the meta-fishriver BSP layer
28========================================= 28=========================================
29 29
30For each BSP in the 'meta-intel' repository, there are multiple
31branches, one corresponding to each major release starting with
32'laverne' (0.90), in addition to the latest code which tracks the
33current master.
34
35In order to build an image with BSP support for a given release, you 30In order to build an image with BSP support for a given release, you
36need to check out the 'meta-intel' branch corresponding to the release 31need to download the corresponding BSP tarball from the 'Board Support
37you're building against e.g. to build for laverne (0.90), check out 32Package (BSP) Downloads' page of the Yocto Project website.
38the 'laverne' branch of both poky and 'meta-intel'.
39 33
40Having done that, and assuming you cloned the 'meta-intel' repository 34Having done that, and assuming you extracted the BSP tarball contents
41at the top-level of your yocto build tree, you can build a fishriver 35at the top-level of your yocto build tree, you can build a fishriver
42image by adding the location of the meta-fishriver layer to 36image by adding the location of the meta-fishriver layer to
43bblayers.conf e.g.: 37bblayers.conf e.g.:
@@ -57,6 +51,15 @@ At the end of a successful build, you should have a live image that
57you can boot from a USB flash drive (see instructions on how to do 51you can boot from a USB flash drive (see instructions on how to do
58that below, in the section 'Booting the images from /binary'). 52that below, in the section 'Booting the images from /binary').
59 53
54As an alternative to downloading the BSP tarball, you can also work
55directly from the meta-intel git repository. For each BSP in the
56'meta-intel' repository, there are multiple branches, one
57corresponding to each major release starting with 'laverne' (0.90), in
58addition to the latest code which tracks the current master. Instead
59of extracting a BSP tarball at the top level of your yocto build tree,
60you can equivalently check out the appropriate branch from the
61meta-intel repository at the same location.
62
60 63
61III. Booting the images in /binary 64III. Booting the images in /binary
62================================== 65==================================