summaryrefslogtreecommitdiffstats
path: root/README.hardware
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2011-04-20 17:25:23 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-04-21 00:29:30 +0100
commit6e95cb246f39e4d49d46761b9a7d51c858ac7e9d (patch)
tree1646acfdc315d3dfcc2516a6f49509ba7f633fae /README.hardware
parent4d609d502161137620c4b1901cc225f9e871c3dc (diff)
downloadpoky-6e95cb246f39e4d49d46761b9a7d51c858ac7e9d.tar.gz
poky-6e95cb246f39e4d49d46761b9a7d51c858ac7e9d.tar.bz2
poky-6e95cb246f39e4d49d46761b9a7d51c858ac7e9d.zip
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.hardware20
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:
1. Build a directdisk image format. This will generate proper partition tables
that will in turn be written to the physical media. For example:
- $ bitbake poky-image-minimal-directdisk
+ $ bitbake core-image-minimal-directdisk
2. Use the "dd" utility to write the image to the raw block device. For example:
- # dd if=poky-image-minimal-directdisk-atom-pc.hdddirect of=/dev/sdb
+ # dd if=core-image-minimal-directdisk-atom-pc.hdddirect of=/dev/sdb
USB Device:
1. Build an hddimg image format. This is a simple filesystem without partition
tables and is suitable for USB keys. For example:
- $ bitbake poky-image-minimal-live
+ $ bitbake core-image-minimal-live
2. Use the "dd" utility to write the image to the raw block device. For
example:
- # dd if=poky-image-minimal-live-atom-pc.hddimg of=/dev/sdb
+ # dd if=core-image-minimal-live-atom-pc.hddimg of=/dev/sdb
If the device fails to boot with "Boot error" displayed, it is likely the BIOS
cannot understand the physical layout of the disk (or rather it expects a
@@ -126,7 +126,7 @@ USB Device:
b. Copy the contents of the poky image to the USB-ZIP mode device:
- # mount -o loop poky-image-minimal-live-atom-pc.hddimg /tmp/image
+ # mount -o loop core-image-minimal-live-atom-pc.hddimg /tmp/image
# mount /dev/sdb4 /tmp/usbkey
# cp -rf /tmp/image/* /tmp/usbkey
@@ -185,7 +185,7 @@ and may require modification of the NAND environment.
# cp u-boot-beagleboard.bin /media/boot/u-boot.bin
3. Install the root filesystem
- # tar x -C /media/root -f poky-image-$IMAGE_TYPE-beagleboard.tar.bz2
+ # tar x -C /media/root -f core-image-$IMAGE_TYPE-beagleboard.tar.bz2
# tar x -C /media/root -f modules-$KERNEL_VERSION-beagleboard.tgz
4. Install the kernel uImage
@@ -279,11 +279,11 @@ name in all commands where appropriate.
--- Preparation ---
-1) Build an image (e.g. poky-image-minimal) using "routerstationpro" as the
+1) Build an image (e.g. core-image-minimal) using "routerstationpro" as the
MACHINE
2) Partition the USB drive so that primary partition 1 is type Linux (83).
-Minimum size depends on your root image size - poky-image-minimal probably
+Minimum size depends on your root image size - core-image-minimal probably
only needs 8-16MB, other images will need more.
# fdisk /dev/sdb
@@ -304,11 +304,11 @@ only needs 8-16MB, other images will need more.
# mke2fs -j /dev/sdb1
4) Mount partition 1 and then extract the contents of
-tmp/deploy/images/poky-image-XXXX.tar.bz2 into it (preserving permissions).
+tmp/deploy/images/core-image-XXXX.tar.bz2 into it (preserving permissions).
# mount /dev/sdb1 /media/sdb1
# cd /media/sdb1
- # tar -xvjpf tmp/deploy/images/poky-image-XXXX.tar.bz2
+ # tar -xvjpf tmp/deploy/images/core-image-XXXX.tar.bz2
5) Unmount the USB drive and then plug it into the board's USB port