diff options
author | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-04-20 17:25:23 +0100 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-04-21 00:29:30 +0100 |
commit | 6e95cb246f39e4d49d46761b9a7d51c858ac7e9d (patch) | |
tree | 1646acfdc315d3dfcc2516a6f49509ba7f633fae /README.hardware | |
parent | 4d609d502161137620c4b1901cc225f9e871c3dc (diff) | |
download | poky-6e95cb246f39e4d49d46761b9a7d51c858ac7e9d.tar.gz |
Rename poky-image-* -> core-image-* and task-poky-* -> task-core-*
(From OE-Core rev: 560b04181d8f51d189b99f01a72f17210dadf7a3)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'README.hardware')
-rw-r--r-- | README.hardware | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/README.hardware b/README.hardware index b2ce14661e..b895f8fa13 100644 --- a/README.hardware +++ b/README.hardware | |||
@@ -87,22 +87,22 @@ Hard Disk: | |||
87 | 1. Build a directdisk image format. This will generate proper partition tables | 87 | 1. Build a directdisk image format. This will generate proper partition tables |
88 | that will in turn be written to the physical media. For example: | 88 | that will in turn be written to the physical media. For example: |
89 | 89 | ||
90 | $ bitbake poky-image-minimal-directdisk | 90 | $ bitbake core-image-minimal-directdisk |
91 | 91 | ||
92 | 2. Use the "dd" utility to write the image to the raw block device. For example: | 92 | 2. Use the "dd" utility to write the image to the raw block device. For example: |
93 | 93 | ||
94 | # dd if=poky-image-minimal-directdisk-atom-pc.hdddirect of=/dev/sdb | 94 | # dd if=core-image-minimal-directdisk-atom-pc.hdddirect of=/dev/sdb |
95 | 95 | ||
96 | USB Device: | 96 | USB Device: |
97 | 1. Build an hddimg image format. This is a simple filesystem without partition | 97 | 1. Build an hddimg image format. This is a simple filesystem without partition |
98 | tables and is suitable for USB keys. For example: | 98 | tables and is suitable for USB keys. For example: |
99 | 99 | ||
100 | $ bitbake poky-image-minimal-live | 100 | $ bitbake core-image-minimal-live |
101 | 101 | ||
102 | 2. Use the "dd" utility to write the image to the raw block device. For | 102 | 2. Use the "dd" utility to write the image to the raw block device. For |
103 | example: | 103 | example: |
104 | 104 | ||
105 | # dd if=poky-image-minimal-live-atom-pc.hddimg of=/dev/sdb | 105 | # dd if=core-image-minimal-live-atom-pc.hddimg of=/dev/sdb |
106 | 106 | ||
107 | If the device fails to boot with "Boot error" displayed, it is likely the BIOS | 107 | If the device fails to boot with "Boot error" displayed, it is likely the BIOS |
108 | cannot understand the physical layout of the disk (or rather it expects a | 108 | cannot understand the physical layout of the disk (or rather it expects a |
@@ -126,7 +126,7 @@ USB Device: | |||
126 | 126 | ||
127 | b. Copy the contents of the poky image to the USB-ZIP mode device: | 127 | b. Copy the contents of the poky image to the USB-ZIP mode device: |
128 | 128 | ||
129 | # mount -o loop poky-image-minimal-live-atom-pc.hddimg /tmp/image | 129 | # mount -o loop core-image-minimal-live-atom-pc.hddimg /tmp/image |
130 | # mount /dev/sdb4 /tmp/usbkey | 130 | # mount /dev/sdb4 /tmp/usbkey |
131 | # cp -rf /tmp/image/* /tmp/usbkey | 131 | # cp -rf /tmp/image/* /tmp/usbkey |
132 | 132 | ||
@@ -185,7 +185,7 @@ and may require modification of the NAND environment. | |||
185 | # cp u-boot-beagleboard.bin /media/boot/u-boot.bin | 185 | # cp u-boot-beagleboard.bin /media/boot/u-boot.bin |
186 | 186 | ||
187 | 3. Install the root filesystem | 187 | 3. Install the root filesystem |
188 | # tar x -C /media/root -f poky-image-$IMAGE_TYPE-beagleboard.tar.bz2 | 188 | # tar x -C /media/root -f core-image-$IMAGE_TYPE-beagleboard.tar.bz2 |
189 | # tar x -C /media/root -f modules-$KERNEL_VERSION-beagleboard.tgz | 189 | # tar x -C /media/root -f modules-$KERNEL_VERSION-beagleboard.tgz |
190 | 190 | ||
191 | 4. Install the kernel uImage | 191 | 4. Install the kernel uImage |
@@ -279,11 +279,11 @@ name in all commands where appropriate. | |||
279 | 279 | ||
280 | --- Preparation --- | 280 | --- Preparation --- |
281 | 281 | ||
282 | 1) Build an image (e.g. poky-image-minimal) using "routerstationpro" as the | 282 | 1) Build an image (e.g. core-image-minimal) using "routerstationpro" as the |
283 | MACHINE | 283 | MACHINE |
284 | 284 | ||
285 | 2) Partition the USB drive so that primary partition 1 is type Linux (83). | 285 | 2) Partition the USB drive so that primary partition 1 is type Linux (83). |
286 | Minimum size depends on your root image size - poky-image-minimal probably | 286 | Minimum size depends on your root image size - core-image-minimal probably |
287 | only needs 8-16MB, other images will need more. | 287 | only needs 8-16MB, other images will need more. |
288 | 288 | ||
289 | # fdisk /dev/sdb | 289 | # fdisk /dev/sdb |
@@ -304,11 +304,11 @@ only needs 8-16MB, other images will need more. | |||
304 | # mke2fs -j /dev/sdb1 | 304 | # mke2fs -j /dev/sdb1 |
305 | 305 | ||
306 | 4) Mount partition 1 and then extract the contents of | 306 | 4) Mount partition 1 and then extract the contents of |
307 | tmp/deploy/images/poky-image-XXXX.tar.bz2 into it (preserving permissions). | 307 | tmp/deploy/images/core-image-XXXX.tar.bz2 into it (preserving permissions). |
308 | 308 | ||
309 | # mount /dev/sdb1 /media/sdb1 | 309 | # mount /dev/sdb1 /media/sdb1 |
310 | # cd /media/sdb1 | 310 | # cd /media/sdb1 |
311 | # tar -xvjpf tmp/deploy/images/poky-image-XXXX.tar.bz2 | 311 | # tar -xvjpf tmp/deploy/images/core-image-XXXX.tar.bz2 |
312 | 312 | ||
313 | 5) Unmount the USB drive and then plug it into the board's USB port | 313 | 5) Unmount the USB drive and then plug it into the board's USB port |
314 | 314 | ||