From: Tom Zanussi <tom.zanussi@...>

Update meta-emenlow to reflect the new image names and a couple
other minor cleanups.

Signed-off-by: Tom Zanussi <tom.zanussi@...>
---
meta-emenlow/README | 15 ++++++++-------
1 files changed, 8 insertions(+), 7 deletions(-)

diff --git a/meta-emenlow/README b/meta-emenlow/README
index 6592a70..fc3317e 100644
--- a/meta-emenlow/README
+++ b/meta-emenlow/README
@@ -40,8 +40,8 @@ To enable the emenlow layer, add the emenlow MACHINE to local.conf:

You should then be able to build an emenlow image as such:

- $ source poky-init-build-env
- $ bitbake poky-image-sato-live
+ $ source oe-init-build-env
+ $ bitbake core-image-sato

At the end of a successful build, you should have a live image that
you can boot from a USB flash drive (see instructions on how to do
@@ -51,10 +51,11 @@ As an alternative to downloading the BSP tarball, you can also work
directly from the meta-intel git repository. For each BSP in the
'meta-intel' repository, there are multiple branches, one
corresponding to each major release starting with 'laverne' (0.90), in
-addition to the latest code which tracks the current master. Instead
-of extracting a BSP tarball at the top level of your yocto build tree,
-you can equivalently check out the appropriate branch from the
-meta-intel repository at the same location.
+addition to the latest code which tracks the current master (note that
+not all BSPs are present in every release). Instead of extracting a
+BSP tarball at the top level of your yocto build tree, you can
+equivalently check out the appropriate branch from the meta-intel
+repository at the same location.


II. Booting the images in /binary
@@ -67,7 +68,7 @@ Under Linux, insert a USB flash drive. Assuming the USB flash drive
takes device /dev/sdf, use dd to copy the live image to it. For
example:

-# dd if=poky-image-sato-live-emenlow-20101207053738.hddimg of=/dev/sdf
+# dd if=core-image-sato-emenlow-20101207053738.hddimg of=/dev/sdf
# sync
# eject /dev/sdf

--
1.7.0.4