meta-intel: README updates
cover meta-intel: README updates
From: Tom Zanussi <[email protected]>
Some minor updates to the meta-intel BSP README files.
The following changes since commit 527d0c90cc37ca988745578e213fb451fd6a6fe4:
Tom Zanussi (1):
xpsb-glx: Move the pkgconfig file(s) to the -dev package
are available in the git repository at:
git://git.yoctoproject.org/meta-intel.git tzanussi/readme-updates
http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel/log/?h=tzanussi/readme-updates
Tom Zanussi (4):
meta-emenlow: update README
meta-fishriver: update README
meta-jasperforest: update README
meta-sugarbay: update README
meta-emenlow/README | 15 ++++++++------- meta-fishriver/README | 28 ++++++++++++++-------------- meta-jasperforest/README | 15 ++++++++------- meta-sugarbay/README | 18 +++++++++--------- 4 files changed, 39 insertions(+), 37 deletions(-)
PATCH 1/4 meta-emenlow: update README
From: Tom Zanussi <[email protected]>
Update meta-emenlow to reflect the new image names and a couple other minor cleanups.
Signed-off-by Tom Zanussi <[email protected]>
--- meta-emenlow/README | 15 ++++++++------- 1 files changed, 8 insertions(+), 7 deletions(-)
meta-emenlow/README +8 -7
@@ -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
Signature · 1 line
1.7.0.4
PATCH 2/4 meta-fishriver: update README
From: Tom Zanussi <[email protected]>
Update meta-fishriver to reflect the new image names and a couple other minor cleanups.
Signed-off-by Tom Zanussi <[email protected]>
--- meta-fishriver/README | 28 ++++++++++++++-------------- 1 files changed, 14 insertions(+), 14 deletions(-)
meta-fishriver/README +14 -14
@@ -6,13 +6,12 @@ Please see the corresponding sections below for details. Table of Contents ================= - I. Special notes on the meta-fishriver BSP layer - II. Building the meta-fishriver BSP layer -III. Booting the images in /binary + I. Building the meta-fishriver BSP layer + II. Booting the images in /binary -II. Building the meta-fishriver BSP layer -========================================= +I. Building the meta-fishriver BSP layer +======================================== In order to build an image with BSP support for a given release, you 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: You should then be able to build a fishriver 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
@@ -42,14 +41,15 @@ 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. -III. Booting the images in /binary -================================== +II. Booting the images in /binary +================================= This BSP contains bootable live images, which can be used to directly boot Yocto off of a USB flash drive.
@@ -58,7 +58,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-fishriver-20101207053738.hddimg of=/dev/sdf +# dd if=core-image-sato-fishriver-20101207053738.hddimg of=/dev/sdf # sync # eject /dev/sdf
Signature · 1 line
1.7.0.4
PATCH 3/4 meta-jasperforest: update README
In reply to [email protected]From: Tom Zanussi <[email protected]>
Update meta-jasperforest to reflect the new image names and a couple other minor cleanups.
Signed-off-by Tom Zanussi <[email protected]>
--- meta-jasperforest/README | 15 ++++++++------- 1 files changed, 8 insertions(+), 7 deletions(-)
meta-jasperforest/README +8 -7
@@ -35,8 +35,8 @@ To enable the jasperforest layer, add the jasperforest MACHINE to local.conf: You should then be able to build a jasperforest 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
@@ -46,10 +46,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
@@ -62,7 +63,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-jasperforest-20101207053738.hddimg of=/dev/sdf +# dd if=core-image-sato-jasperforest-20101207053738.hddimg of=/dev/sdf # sync # eject /dev/sdf
Signature · 1 line
1.7.0.4
PATCH 4/4 meta-sugarbay: update README
In reply to [email protected]From: Tom Zanussi <[email protected]>
Update meta-sugarbay to reflect the new image names and a couple other minor cleanups.
Signed-off-by Tom Zanussi <[email protected]>
--- meta-sugarbay/README | 18 +++++++++--------- 1 files changed, 9 insertions(+), 9 deletions(-)
meta-sugarbay/README +9 -9
@@ -10,8 +10,7 @@ Table of Contents ================= I. Building the meta-sugarbay BSP layer - II. Special notes for building the meta-sugarbay BSP layer -III. Booting the images in /binary + II. Booting the images in /binary I. Building the meta-sugarbay BSP layer
@@ -34,8 +33,8 @@ To enable the sugarbay layer, add the sugarbay MACHINE to local.conf: You should then be able to build a sugarbay 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
@@ -45,10 +44,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
@@ -61,7 +61,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-sugarbay-20101207053738.hddimg of=/dev/sdf +# dd if=core-image-sato-sugarbay-20101207053738.hddimg of=/dev/sdf # sync # eject /dev/sdf
Signature · 1 line
1.7.0.4