summaryrefslogtreecommitdiffstats
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
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>
-rw-r--r--meta-crownbay/README21
-rw-r--r--meta-emenlow/README20
-rw-r--r--meta-fishriver/README21
-rw-r--r--meta-jasperforest/README21
4 files changed, 48 insertions, 35 deletions
diff --git a/meta-crownbay/README b/meta-crownbay/README
index 1177024..bb1e0c3 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==========================================================
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=================================
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==================================
diff --git a/meta-jasperforest/README b/meta-jasperforest/README
index ab7246d..6421d06 100644
--- a/meta-jasperforest/README
+++ b/meta-jasperforest/README
@@ -18,17 +18,11 @@ Table of Contents
18I. Building the meta-jasperforest BSP layer 18I. Building the meta-jasperforest BSP layer
19======================================= 19=======================================
20 20
21For each BSP in the 'meta-intel' repository, there are multiple
22branches, one corresponding to each major release starting with
23'laverne' (0.90), in addition to the latest code which tracks the
24current master.
25
26In order to build an image with BSP support for a given release, you 21In order to build an image with BSP support for a given release, you
27need to check out the 'meta-intel' branch corresponding to the release 22need to download the corresponding BSP tarball from the 'Board Support
28you're building against e.g. to build for laverne (0.90), check out 23Package (BSP) Downloads' page of the Yocto Project website.
29the 'laverne' branch of both poky and 'meta-intel'.
30 24
31Having done that, and assuming you cloned the 'meta-intel' repository 25Having done that, and assuming you extracted the BSP tarball contents
32at the top-level of your yocto build tree, you can build a jasperforest 26at the top-level of your yocto build tree, you can build a jasperforest
33image by adding the location of the meta-jasperforest layer to 27image by adding the location of the meta-jasperforest layer to
34bblayers.conf e.g.: 28bblayers.conf e.g.:
@@ -48,6 +42,15 @@ At the end of a successful build, you should have a live image that
48you can boot from a USB flash drive (see instructions on how to do 42you can boot from a USB flash drive (see instructions on how to do
49that below, in the section 'Booting the images from /binary'). 43that below, in the section 'Booting the images from /binary').
50 44
45As an alternative to downloading the BSP tarball, you can also work
46directly from the meta-intel git repository. For each BSP in the
47'meta-intel' repository, there are multiple branches, one
48corresponding to each major release starting with 'laverne' (0.90), in
49addition to the latest code which tracks the current master. Instead
50of extracting a BSP tarball at the top level of your yocto build tree,
51you can equivalently check out the appropriate branch from the
52meta-intel repository at the same location.
53
51 54
52II. Booting the images in /binary 55II. Booting the images in /binary
53================================= 56=================================