* [PATCH 1/3] yocto-layer / yocto-bsp: tweak layer.conf comment
2013-04-09 14:21 [PATCH 0/3] Minor comment/doc fixes for Poky Paul Eggleton
@ 2013-04-09 14:21 ` Paul Eggleton
2013-04-09 14:21 ` [PATCH 2/3] meta-yocto*/conf/layer.conf: tweak BBFILES comments Paul Eggleton
2013-04-09 14:22 ` [PATCH 3/3] README.hardware: bring up-to-date Paul Eggleton
2 siblings, 0 replies; 4+ messages in thread
From: Paul Eggleton @ 2013-04-09 14:21 UTC (permalink / raw)
To: poky
We have recipes-* directories not a recipes directory; this is left over
from the old old layout (2010).
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
---
scripts/lib/bsp/substrate/target/arch/common/conf/layer.conf | 2 +-
scripts/lib/bsp/substrate/target/arch/layer/conf/layer.conf | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/scripts/lib/bsp/substrate/target/arch/common/conf/layer.conf b/scripts/lib/bsp/substrate/target/arch/common/conf/layer.conf
index 97029dd..5529f45 100644
--- a/scripts/lib/bsp/substrate/target/arch/common/conf/layer.conf
+++ b/scripts/lib/bsp/substrate/target/arch/common/conf/layer.conf
@@ -1,7 +1,7 @@
# We have a conf and classes directory, add to BBPATH
BBPATH .= ":${LAYERDIR}"
-# We have a recipes directory, add to BBFILES
+# We have a recipes-* directories, add to BBFILES
BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/recipes-*/*/*.bbappend"
diff --git a/scripts/lib/bsp/substrate/target/arch/layer/conf/layer.conf b/scripts/lib/bsp/substrate/target/arch/layer/conf/layer.conf
index 76153f3..bdffe17 100644
--- a/scripts/lib/bsp/substrate/target/arch/layer/conf/layer.conf
+++ b/scripts/lib/bsp/substrate/target/arch/layer/conf/layer.conf
@@ -1,7 +1,7 @@
# We have a conf and classes directory, add to BBPATH
BBPATH .= ":${LAYERDIR}"
-# We have a recipes directory, add to BBFILES
+# We have recipes-* directories, add to BBFILES
BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/recipes-*/*/*.bbappend"
--
1.7.10.4
^ permalink raw reply related [flat|nested] 4+ messages in thread* [PATCH 2/3] meta-yocto*/conf/layer.conf: tweak BBFILES comments
2013-04-09 14:21 [PATCH 0/3] Minor comment/doc fixes for Poky Paul Eggleton
2013-04-09 14:21 ` [PATCH 1/3] yocto-layer / yocto-bsp: tweak layer.conf comment Paul Eggleton
@ 2013-04-09 14:21 ` Paul Eggleton
2013-04-09 14:22 ` [PATCH 3/3] README.hardware: bring up-to-date Paul Eggleton
2 siblings, 0 replies; 4+ messages in thread
From: Paul Eggleton @ 2013-04-09 14:21 UTC (permalink / raw)
To: poky
"packages" was the old name (pre-2010) under which the recipe files were
stored.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
---
meta-yocto-bsp/conf/layer.conf | 2 +-
meta-yocto/conf/layer.conf | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta-yocto-bsp/conf/layer.conf b/meta-yocto-bsp/conf/layer.conf
index 18544bd..2be7cc3 100644
--- a/meta-yocto-bsp/conf/layer.conf
+++ b/meta-yocto-bsp/conf/layer.conf
@@ -1,7 +1,7 @@
# We have a conf and classes directory, add to BBPATH
BBPATH .= ":${LAYERDIR}"
-# We have a packages directory, add to BBFILES
+# We have recipes-* directories, add to BBFILES
BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/recipes-*/*/*.bbappend"
diff --git a/meta-yocto/conf/layer.conf b/meta-yocto/conf/layer.conf
index 89ed171..e012f24 100644
--- a/meta-yocto/conf/layer.conf
+++ b/meta-yocto/conf/layer.conf
@@ -1,7 +1,7 @@
# We have a conf and classes directory, add to BBPATH
BBPATH =. "${LAYERDIR}:"
-# We have a packages directory, add to BBFILES
+# We have recipes-* directories, add to BBFILES
BBFILES += "${LAYERDIR}/recipes-*/*/*.bb \
${LAYERDIR}/recipes-*/*/*.bbappend"
--
1.7.10.4
^ permalink raw reply related [flat|nested] 4+ messages in thread* [PATCH 3/3] README.hardware: bring up-to-date
2013-04-09 14:21 [PATCH 0/3] Minor comment/doc fixes for Poky Paul Eggleton
2013-04-09 14:21 ` [PATCH 1/3] yocto-layer / yocto-bsp: tweak layer.conf comment Paul Eggleton
2013-04-09 14:21 ` [PATCH 2/3] meta-yocto*/conf/layer.conf: tweak BBFILES comments Paul Eggleton
@ 2013-04-09 14:22 ` Paul Eggleton
2 siblings, 0 replies; 4+ messages in thread
From: Paul Eggleton @ 2013-04-09 14:22 UTC (permalink / raw)
To: poky
* Fix Yocto Project documentation URL
* Indicate physical reference hardware support comes from meta-yocto-bsp
* Remove/replace references to Poky where appropriate
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
---
README.hardware | 51 +++++++++++++++++++++++++++++----------------------
1 file changed, 29 insertions(+), 22 deletions(-)
diff --git a/README.hardware b/README.hardware
index d48c953..ad2fe89 100644
--- a/README.hardware
+++ b/README.hardware
@@ -1,28 +1,34 @@
Poky Hardware README
====================
-This file gives details about using Poky with different hardware reference
-boards and consumer devices. A full list of target machines can be found by
-looking in the meta/conf/machine/ directory. If in doubt about using Poky with
-your hardware, consult the documentation for your board/device.
+This file gives details about using Poky with the reference machines
+supported out of the box. A full list of supported reference target machines
+can be found by looking in the following directories:
+
+ meta/conf/machine/
+ meta-yocto-bsp/conf/machine/
+
+If you are in doubt about using Poky/OpenEmbedded with your hardware, consult
+the documentation for your board/device.
Support for additional devices is normally added by creating BSP layers - for
more information please see the Yocto Board Support Package (BSP) Developer's
Guide - documentation source is in documentation/bspguide or download the PDF
from:
- http://yoctoproject.org/community/documentation
+ http://yoctoproject.org/documentation
-Support for machines other than QEMU may be moved out to separate BSP layers in
-future versions.
+Support for physical reference hardware has now been split out into a
+meta-yocto-bsp layer which can be removed separately from other layers if not
+needed.
QEMU Emulation Targets
======================
-To simplify development Poky supports building images to work with the QEMU
-emulator in system emulation mode. Several architectures are currently
-supported:
+To simplify development, the build system supports building images to
+work with the QEMU emulator in system emulation mode. Several architectures
+are currently supported:
* ARM (qemuarm)
* x86 (qemux86)
@@ -30,32 +36,33 @@ supported:
* PowerPC (qemuppc)
* MIPS (qemumips)
-Use of the QEMU images is covered in the Poky Reference Manual. The Poky
-MACHINE setting corresponding to the target is given in brackets.
+Use of the QEMU images is covered in the Yocto Project Reference Manual.
+The appropriate MACHINE variable value corresponding to the target is given
+in brackets.
Hardware Reference Boards
=========================
-The following boards are supported by Poky's core layer:
+The following boards are supported by the meta-yocto-bsp layer:
* Texas Instruments Beagleboard (beagleboard)
* Freescale MPC8315E-RDB (mpc8315e-rdb)
* Ubiquiti Networks RouterStation Pro (routerstationpro)
-For more information see the board's section below. The Poky MACHINE setting
-corresponding to the board is given in brackets.
+For more information see the board's section below. The appropriate MACHINE
+variable value corresponding to the board is given in brackets.
Consumer Devices
================
-The following consumer devices are supported by Poky's core layer:
+The following consumer devices are supported by the meta-yocto-bsp layer:
* Intel Atom based PCs and devices (atom-pc)
-For more information see the device's section below. The Poky MACHINE setting
-corresponding to the device is given in brackets.
+For more information see the device's section below. The appropriate MACHINE
+variable value corresponding to the device is given in brackets.
@@ -78,7 +85,7 @@ supports ethernet, wifi, sound, and i915 graphics by default in addition to
common PC input devices, busses, and so on.
Depending on the device, it can boot from a traditional hard-disk, a USB device,
-or over the network. Writing poky generated images to physical media is
+or over the network. Writing generated images to physical media is
straightforward with a caveat for USB devices. The following examples assume the
target boot device is /dev/sdb, be sure to verify this and use the correct
device as the following commands are run as root and are not reversable.
@@ -131,7 +138,7 @@ USB Device:
device stops flashing, remove and reinsert the device to allow the
kernel to detect the new partition layout.
- c. Copy the contents of the poky image to the USB-ZIP mode device:
+ c. Copy the contents of the image to the USB-ZIP mode device:
# mkdir /tmp/image
# mkdir /tmp/usbkey
@@ -281,8 +288,8 @@ anything here.
Load the kernel and dtb (device tree blob), and boot the system as follows:
1. Get the kernel (uImage-mpc8315e-rdb.bin) and dtb (uImage-mpc8315e-rdb.dtb)
- files from the Poky build tmp/deploy directory, and make them available on
- your TFTP server.
+ files from the tmp/deploy directory, and make them available on your TFTP
+ server.
2. Connect the board's first serial port to your workstation and then start up
your favourite serial terminal so that you will be able to interact with
--
1.7.10.4
^ permalink raw reply related [flat|nested] 4+ messages in thread