summaryrefslogtreecommitdiffstats
path: root/README.hardware
diff options
context:
space:
mode:
Diffstat (limited to 'README.hardware')
-rw-r--r--README.hardware51
1 files 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 @@
1 Poky Hardware README 1 Poky Hardware README
2 ==================== 2 ====================
3 3
4This file gives details about using Poky with different hardware reference 4This file gives details about using Poky with the reference machines
5boards and consumer devices. A full list of target machines can be found by 5supported out of the box. A full list of supported reference target machines
6looking in the meta/conf/machine/ directory. If in doubt about using Poky with 6can be found by looking in the following directories:
7your hardware, consult the documentation for your board/device. 7
8 meta/conf/machine/
9 meta-yocto-bsp/conf/machine/
10
11If you are in doubt about using Poky/OpenEmbedded with your hardware, consult
12the documentation for your board/device.
8 13
9Support for additional devices is normally added by creating BSP layers - for 14Support for additional devices is normally added by creating BSP layers - for
10more information please see the Yocto Board Support Package (BSP) Developer's 15more information please see the Yocto Board Support Package (BSP) Developer's
11Guide - documentation source is in documentation/bspguide or download the PDF 16Guide - documentation source is in documentation/bspguide or download the PDF
12from: 17from:
13 18
14 http://yoctoproject.org/community/documentation 19 http://yoctoproject.org/documentation
15 20
16Support for machines other than QEMU may be moved out to separate BSP layers in 21Support for physical reference hardware has now been split out into a
17future versions. 22meta-yocto-bsp layer which can be removed separately from other layers if not
23needed.
18 24
19 25
20QEMU Emulation Targets 26QEMU Emulation Targets
21====================== 27======================
22 28
23To simplify development Poky supports building images to work with the QEMU 29To simplify development, the build system supports building images to
24emulator in system emulation mode. Several architectures are currently 30work with the QEMU emulator in system emulation mode. Several architectures
25supported: 31are currently supported:
26 32
27 * ARM (qemuarm) 33 * ARM (qemuarm)
28 * x86 (qemux86) 34 * x86 (qemux86)
@@ -30,32 +36,33 @@ supported:
30 * PowerPC (qemuppc) 36 * PowerPC (qemuppc)
31 * MIPS (qemumips) 37 * MIPS (qemumips)
32 38
33Use of the QEMU images is covered in the Poky Reference Manual. The Poky 39Use of the QEMU images is covered in the Yocto Project Reference Manual.
34MACHINE setting corresponding to the target is given in brackets. 40The appropriate MACHINE variable value corresponding to the target is given
41in brackets.
35 42
36 43
37Hardware Reference Boards 44Hardware Reference Boards
38========================= 45=========================
39 46
40The following boards are supported by Poky's core layer: 47The following boards are supported by the meta-yocto-bsp layer:
41 48
42 * Texas Instruments Beagleboard (beagleboard) 49 * Texas Instruments Beagleboard (beagleboard)
43 * Freescale MPC8315E-RDB (mpc8315e-rdb) 50 * Freescale MPC8315E-RDB (mpc8315e-rdb)
44 * Ubiquiti Networks RouterStation Pro (routerstationpro) 51 * Ubiquiti Networks RouterStation Pro (routerstationpro)
45 52
46For more information see the board's section below. The Poky MACHINE setting 53For more information see the board's section below. The appropriate MACHINE
47corresponding to the board is given in brackets. 54variable value corresponding to the board is given in brackets.
48 55
49 56
50Consumer Devices 57Consumer Devices
51================ 58================
52 59
53The following consumer devices are supported by Poky's core layer: 60The following consumer devices are supported by the meta-yocto-bsp layer:
54 61
55 * Intel Atom based PCs and devices (atom-pc) 62 * Intel Atom based PCs and devices (atom-pc)
56 63
57For more information see the device's section below. The Poky MACHINE setting 64For more information see the device's section below. The appropriate MACHINE
58corresponding to the device is given in brackets. 65variable value corresponding to the device is given in brackets.
59 66
60 67
61 68
@@ -78,7 +85,7 @@ supports ethernet, wifi, sound, and i915 graphics by default in addition to
78common PC input devices, busses, and so on. 85common PC input devices, busses, and so on.
79 86
80Depending on the device, it can boot from a traditional hard-disk, a USB device, 87Depending on the device, it can boot from a traditional hard-disk, a USB device,
81or over the network. Writing poky generated images to physical media is 88or over the network. Writing generated images to physical media is
82straightforward with a caveat for USB devices. The following examples assume the 89straightforward with a caveat for USB devices. The following examples assume the
83target boot device is /dev/sdb, be sure to verify this and use the correct 90target boot device is /dev/sdb, be sure to verify this and use the correct
84device as the following commands are run as root and are not reversable. 91device as the following commands are run as root and are not reversable.
@@ -131,7 +138,7 @@ USB Device:
131 device stops flashing, remove and reinsert the device to allow the 138 device stops flashing, remove and reinsert the device to allow the
132 kernel to detect the new partition layout. 139 kernel to detect the new partition layout.
133 140
134 c. Copy the contents of the poky image to the USB-ZIP mode device: 141 c. Copy the contents of the image to the USB-ZIP mode device:
135 142
136 # mkdir /tmp/image 143 # mkdir /tmp/image
137 # mkdir /tmp/usbkey 144 # mkdir /tmp/usbkey
@@ -281,8 +288,8 @@ anything here.
281Load the kernel and dtb (device tree blob), and boot the system as follows: 288Load the kernel and dtb (device tree blob), and boot the system as follows:
282 289
283 1. Get the kernel (uImage-mpc8315e-rdb.bin) and dtb (uImage-mpc8315e-rdb.dtb) 290 1. Get the kernel (uImage-mpc8315e-rdb.bin) and dtb (uImage-mpc8315e-rdb.dtb)
284 files from the Poky build tmp/deploy directory, and make them available on 291 files from the tmp/deploy directory, and make them available on your TFTP
285 your TFTP server. 292 server.
286 293
287 2. Connect the board's first serial port to your workstation and then start up 294 2. Connect the board's first serial port to your workstation and then start up
288 your favourite serial terminal so that you will be able to interact with 295 your favourite serial terminal so that you will be able to interact with