path: root/README.hardware
diff options
authorSaul Wold <>2016-10-09 08:24:24 -0700
committerRichard Purdie <>2016-10-11 08:28:21 +0100
commitd9809e946b36782440cd729a4610744b7b6795fa (patch)
tree426207a570f01c60789a7fc9186411d2e3b7239a /README.hardware
parent68c64572f6567d925b59c81158320441436270d7 (diff)
README.hardware: Update Genericx86 section
This section was truly dated, update with newer hardware that is being tested. Update section on creating USB stick images using wic and alternate EFI_PROVIDER information about systemd-boot. (From meta-yocto rev: 4a8f28e2c18211a2cd1b380b0b2c8d175fe1e51a) Signed-off-by: Saul Wold <> Signed-off-by: Richard Purdie <>
Diffstat (limited to 'README.hardware')
1 files changed, 17 insertions, 65 deletions
diff --git a/README.hardware b/README.hardware
index 9c74c5d3c3..6383bd71d3 100644
--- a/README.hardware
+++ b/README.hardware
@@ -77,31 +77,22 @@ variable value corresponding to the device is given in brackets.
-Intel x86 based PCs and devices (genericx86)
+Intel x86 based PCs and devices (genericx86*)
-The genericx86 MACHINE is tested on the following platforms:
+The genericx86 and genericx86-64 MACHINE are tested on the following platforms:
Intel Xeon/Core i-Series:
- + Intel Romley Server: Sandy Bridge Xeon processor, C600 PCH (Patsburg), (Canoe Pass CRB)
- + Intel Romley Server: Ivy Bridge Xeon processor, C600 PCH (Patsburg), (Intel SDP S2R3)
- + Intel Crystal Forest Server: Sandy Bridge Xeon processor, DH89xx PCH (Cave Creek), (Stargo CRB)
- + Intel Chief River Mobile: Ivy Bridge Mobile processor, QM77 PCH (Panther Point-M), (Emerald Lake II CRB, Sabino Canyon CRB)
- + Intel Huron River Mobile: Sandy Bridge processor, QM67 PCH (Cougar Point), (Emerald Lake CRB, EVOC EC7-1817LNAR board)
- + Intel Calpella Platform: Core i7 processor, QM57 PCH (Ibex Peak-M), (Red Fort CRB, Emerson MATXM CORE-411-B)
- + Intel Nehalem/Westmere-EP Server: Xeon 56xx/55xx processors, 5520 chipset, ICH10R IOH (82801), (Hanlan Creek CRB)
- + Intel Nehalem Workstation: Xeon 56xx/55xx processors, System SC5650SCWS (Greencity CRB)
- + Intel Picket Post Server: Xeon 56xx/55xx processors (Jasper Forest), 3420 chipset (Ibex Peak), (Osage CRB)
- + Intel Storage Platform: Sandy Bridge Xeon processor, C600 PCH (Patsburg), (Oak Creek Canyon CRB)
- + Intel Shark Bay Client Platform: Haswell processor, LynxPoint PCH, (Walnut Canyon CRB, Lava Canyon CRB, Basking Ridge CRB, Flathead Creek CRB)
- + Intel Shark Bay Ultrabook Platform: Haswell ULT processor, Lynx Point-LP PCH, (WhiteTip Mountain 1 CRB)
+ + Intel NUC5 Series - ix-52xx Series SOC (Broadwell)
+ + Intel NUC6 Series - ix-62xx Series SOC (Skylake)
+ + Intel Shumway Xeon Server
Intel Atom platforms:
- + Intel embedded Menlow: Intel Atom Z510/530 CPU, System Controller Hub US15W (Portwell NANO-8044)
- + Intel Luna Pier: Intel Atom N4xx/D5xx series CPU (aka: Pineview-D & -M), 82801HM I/O Hub (ICH8M), (Advantech AIMB-212, Moon Creek CRB)
- + Intel Queens Bay platform: Intel Atom E6xx CPU (aka: Tunnel Creek), Topcliff EG20T I/O Hub (Emerson NITX-315, Crown Bay CRB, Minnow Board)
- + Intel Fish River Island platform: Intel Atom E6xx CPU (aka: Tunnel Creek), Topcliff EG20T I/O Hub (Kontron KM2M806)
- + Intel Cedar Trail platform: Intel Atom N2000 & D2000 series CPU (aka: Cedarview), NM10 Express Chipset (Norco kit BIS-6630, Cedar Rock CRB)
+ + MinnowBoard MAX - E3825 SOC (Bay Trail)
+ + MinnowBoard MAX - Turbot (ADI Engineering) - E3826 SOC (Bay Trail)
+ - These boards can be either 32bot or 64bit modes depending on firmware
+ - See for details
+ + Intel Braswell SOC
and is likely to work on many unlisted Atom/Core/Xeon based devices. The MACHINE
type supports ethernet, wifi, sound, and Intel/vesa graphics by default in
@@ -136,53 +127,14 @@ USB Device:
device, but the idea is to force BIOS to read the Cylinder/Head/Sector
geometry from the device.
- 2. Without such an option, the BIOS generally boots the device in USB-ZIP
- mode. To write an image to a USB device that will be bootable in
- USB-ZIP mode, carry out the following actions:
+ 2. Use a ".wic" image with an EFI partition
- a. Determine the geometry of your USB device using fdisk:
+ a) With a default grub-efi bootloader:
+ # dd if=core-image-minimal-genericx86-64.wic of=/dev/sdb
- # fdisk /dev/sdb
- Command (m for help): p
- Disk /dev/sdb: 4011 MB, 4011491328 bytes
- 124 heads, 62 sectors/track, 1019 cylinders, total 7834944 sectors
- ...
- Command (m for help): q
- b. Configure the USB device for USB-ZIP mode:
- # mkdiskimage -4 /dev/sdb 1019 124 62
- Where 1019, 124 and 62 are the cylinder, head and sectors/track counts
- as reported by fdisk (substitute the values reported for your device).
- When the operation has finished and the access LED (if any) on the
- device stops flashing, remove and reinsert the device to allow the
- kernel to detect the new partition layout.
- c. Copy the contents of the image to the USB-ZIP mode device:
- # mkdir /tmp/image
- # mkdir /tmp/usbkey
- # mount -o loop core-image-minimal-genericx86.hddimg /tmp/image
- # mount /dev/sdb4 /tmp/usbkey
- # cp -rf /tmp/image/* /tmp/usbkey
- d. Install the syslinux boot loader:
- # syslinux /dev/sdb4
- e. Unmount everything:
- # umount /tmp/image
- # umount /tmp/usbkey
- Install the boot device in the target board and configure the BIOS to boot
- from it.
- For more details on the USB-ZIP scenario, see the syslinux documentation:
+ b) Use systemd-boot instead
+ - Build an image with EFI_PROVIDER="systemd-boot" then use the above
+ dd command to write the image to a USB stick.
Texas Instruments Beaglebone (beaglebone)