diff options
Diffstat (limited to 'meta-fishriver')
-rw-r--r-- | meta-fishriver/README | 28 |
1 files changed, 14 insertions, 14 deletions
diff --git a/meta-fishriver/README b/meta-fishriver/README index 013f76e6..b76056c5 100644 --- a/meta-fishriver/README +++ b/meta-fishriver/README | |||
@@ -6,13 +6,12 @@ Please see the corresponding sections below for details. | |||
6 | Table of Contents | 6 | Table of Contents |
7 | ================= | 7 | ================= |
8 | 8 | ||
9 | I. Special notes on the meta-fishriver BSP layer | 9 | I. Building the meta-fishriver BSP layer |
10 | II. Building the meta-fishriver BSP layer | 10 | II. Booting the images in /binary |
11 | III. Booting the images in /binary | ||
12 | 11 | ||
13 | 12 | ||
14 | II. Building the meta-fishriver BSP layer | 13 | I. Building the meta-fishriver BSP layer |
15 | ========================================= | 14 | ======================================== |
16 | 15 | ||
17 | In order to build an image with BSP support for a given release, you | 16 | In order to build an image with BSP support for a given release, you |
18 | need to download the corresponding BSP tarball from the 'Board Support | 17 | need to download the corresponding BSP tarball from the 'Board Support |
@@ -31,8 +30,8 @@ To enable the fishriver layer, add the fishriver MACHINE to local.conf: | |||
31 | 30 | ||
32 | You should then be able to build a fishriver image as such: | 31 | You should then be able to build a fishriver image as such: |
33 | 32 | ||
34 | $ source poky-init-build-env | 33 | $ source oe-init-build-env |
35 | $ bitbake poky-image-sato-live | 34 | $ bitbake core-image-sato |
36 | 35 | ||
37 | At the end of a successful build, you should have a live image that | 36 | At the end of a successful build, you should have a live image that |
38 | you can boot from a USB flash drive (see instructions on how to do | 37 | you can boot from a USB flash drive (see instructions on how to do |
@@ -42,14 +41,15 @@ As an alternative to downloading the BSP tarball, you can also work | |||
42 | directly from the meta-intel git repository. For each BSP in the | 41 | directly from the meta-intel git repository. For each BSP in the |
43 | 'meta-intel' repository, there are multiple branches, one | 42 | 'meta-intel' repository, there are multiple branches, one |
44 | corresponding to each major release starting with 'laverne' (0.90), in | 43 | corresponding to each major release starting with 'laverne' (0.90), in |
45 | addition to the latest code which tracks the current master. Instead | 44 | addition to the latest code which tracks the current master (note that |
46 | of extracting a BSP tarball at the top level of your yocto build tree, | 45 | not all BSPs are present in every release). Instead of extracting a |
47 | you can equivalently check out the appropriate branch from the | 46 | BSP tarball at the top level of your yocto build tree, you can |
48 | meta-intel repository at the same location. | 47 | equivalently check out the appropriate branch from the meta-intel |
48 | repository at the same location. | ||
49 | 49 | ||
50 | 50 | ||
51 | III. Booting the images in /binary | 51 | II. Booting the images in /binary |
52 | ================================== | 52 | ================================= |
53 | 53 | ||
54 | This BSP contains bootable live images, which can be used to directly | 54 | This BSP contains bootable live images, which can be used to directly |
55 | boot Yocto off of a USB flash drive. | 55 | boot Yocto off of a USB flash drive. |
@@ -58,7 +58,7 @@ Under Linux, insert a USB flash drive. Assuming the USB flash drive | |||
58 | takes device /dev/sdf, use dd to copy the live image to it. For | 58 | takes device /dev/sdf, use dd to copy the live image to it. For |
59 | example: | 59 | example: |
60 | 60 | ||
61 | # dd if=poky-image-sato-live-fishriver-20101207053738.hddimg of=/dev/sdf | 61 | # dd if=core-image-sato-fishriver-20101207053738.hddimg of=/dev/sdf |
62 | # sync | 62 | # sync |
63 | # eject /dev/sdf | 63 | # eject /dev/sdf |
64 | 64 | ||