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