summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSaul Wold <sgw@linux.intel.com>2016-10-09 08:24:24 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-10-11 08:28:21 +0100
commitd9809e946b36782440cd729a4610744b7b6795fa (patch)
tree426207a570f01c60789a7fc9186411d2e3b7239a
parent68c64572f6567d925b59c81158320441436270d7 (diff)
downloadpoky-d9809e946b36782440cd729a4610744b7b6795fa.tar.gz
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 <sgw@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--README.hardware82
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.
77 =============================== 77 ===============================
78 78
79 79
80Intel x86 based PCs and devices (genericx86) 80Intel x86 based PCs and devices (genericx86*)
81========================================== 81=============================================
82 82
83The genericx86 MACHINE is tested on the following platforms: 83The genericx86 and genericx86-64 MACHINE are tested on the following platforms:
84 84
85Intel Xeon/Core i-Series: 85Intel Xeon/Core i-Series:
86 + Intel Romley Server: Sandy Bridge Xeon processor, C600 PCH (Patsburg), (Canoe Pass CRB) 86 + Intel NUC5 Series - ix-52xx Series SOC (Broadwell)
87 + Intel Romley Server: Ivy Bridge Xeon processor, C600 PCH (Patsburg), (Intel SDP S2R3) 87 + Intel NUC6 Series - ix-62xx Series SOC (Skylake)
88 + Intel Crystal Forest Server: Sandy Bridge Xeon processor, DH89xx PCH (Cave Creek), (Stargo CRB) 88 + Intel Shumway Xeon Server
89 + Intel Chief River Mobile: Ivy Bridge Mobile processor, QM77 PCH (Panther Point-M), (Emerald Lake II CRB, Sabino Canyon CRB)
90 + Intel Huron River Mobile: Sandy Bridge processor, QM67 PCH (Cougar Point), (Emerald Lake CRB, EVOC EC7-1817LNAR board)
91 + Intel Calpella Platform: Core i7 processor, QM57 PCH (Ibex Peak-M), (Red Fort CRB, Emerson MATXM CORE-411-B)
92 + Intel Nehalem/Westmere-EP Server: Xeon 56xx/55xx processors, 5520 chipset, ICH10R IOH (82801), (Hanlan Creek CRB)
93 + Intel Nehalem Workstation: Xeon 56xx/55xx processors, System SC5650SCWS (Greencity CRB)
94 + Intel Picket Post Server: Xeon 56xx/55xx processors (Jasper Forest), 3420 chipset (Ibex Peak), (Osage CRB)
95 + Intel Storage Platform: Sandy Bridge Xeon processor, C600 PCH (Patsburg), (Oak Creek Canyon CRB)
96 + Intel Shark Bay Client Platform: Haswell processor, LynxPoint PCH, (Walnut Canyon CRB, Lava Canyon CRB, Basking Ridge CRB, Flathead Creek CRB)
97 + Intel Shark Bay Ultrabook Platform: Haswell ULT processor, Lynx Point-LP PCH, (WhiteTip Mountain 1 CRB)
98 89
99Intel Atom platforms: 90Intel Atom platforms:
100 + Intel embedded Menlow: Intel Atom Z510/530 CPU, System Controller Hub US15W (Portwell NANO-8044) 91 + MinnowBoard MAX - E3825 SOC (Bay Trail)
101 + Intel Luna Pier: Intel Atom N4xx/D5xx series CPU (aka: Pineview-D & -M), 82801HM I/O Hub (ICH8M), (Advantech AIMB-212, Moon Creek CRB) 92 + MinnowBoard MAX - Turbot (ADI Engineering) - E3826 SOC (Bay Trail)
102 + Intel Queens Bay platform: Intel Atom E6xx CPU (aka: Tunnel Creek), Topcliff EG20T I/O Hub (Emerson NITX-315, Crown Bay CRB, Minnow Board) 93 - These boards can be either 32bot or 64bit modes depending on firmware
103 + Intel Fish River Island platform: Intel Atom E6xx CPU (aka: Tunnel Creek), Topcliff EG20T I/O Hub (Kontron KM2M806) 94 - See minnowboard.org for details
104 + Intel Cedar Trail platform: Intel Atom N2000 & D2000 series CPU (aka: Cedarview), NM10 Express Chipset (Norco kit BIS-6630, Cedar Rock CRB) 95 + Intel Braswell SOC
105 96
106and is likely to work on many unlisted Atom/Core/Xeon based devices. The MACHINE 97and is likely to work on many unlisted Atom/Core/Xeon based devices. The MACHINE
107type supports ethernet, wifi, sound, and Intel/vesa graphics by default in 98type supports ethernet, wifi, sound, and Intel/vesa graphics by default in
@@ -136,53 +127,14 @@ USB Device:
136 device, but the idea is to force BIOS to read the Cylinder/Head/Sector 127 device, but the idea is to force BIOS to read the Cylinder/Head/Sector
137 geometry from the device. 128 geometry from the device.
138 129
139 2. Without such an option, the BIOS generally boots the device in USB-ZIP 130 2. Use a ".wic" image with an EFI partition
140 mode. To write an image to a USB device that will be bootable in
141 USB-ZIP mode, carry out the following actions:
142 131
143 a. Determine the geometry of your USB device using fdisk: 132 a) With a default grub-efi bootloader:
133 # dd if=core-image-minimal-genericx86-64.wic of=/dev/sdb
144 134
145 # fdisk /dev/sdb 135 b) Use systemd-boot instead
146 Command (m for help): p 136 - Build an image with EFI_PROVIDER="systemd-boot" then use the above
147 137 dd command to write the image to a USB stick.
148 Disk /dev/sdb: 4011 MB, 4011491328 bytes
149 124 heads, 62 sectors/track, 1019 cylinders, total 7834944 sectors
150 ...
151
152 Command (m for help): q
153
154 b. Configure the USB device for USB-ZIP mode:
155
156 # mkdiskimage -4 /dev/sdb 1019 124 62
157
158 Where 1019, 124 and 62 are the cylinder, head and sectors/track counts
159 as reported by fdisk (substitute the values reported for your device).
160 When the operation has finished and the access LED (if any) on the
161 device stops flashing, remove and reinsert the device to allow the
162 kernel to detect the new partition layout.
163
164 c. Copy the contents of the image to the USB-ZIP mode device:
165
166 # mkdir /tmp/image
167 # mkdir /tmp/usbkey
168 # mount -o loop core-image-minimal-genericx86.hddimg /tmp/image
169 # mount /dev/sdb4 /tmp/usbkey
170 # cp -rf /tmp/image/* /tmp/usbkey
171
172 d. Install the syslinux boot loader:
173
174 # syslinux /dev/sdb4
175
176 e. Unmount everything:
177
178 # umount /tmp/image
179 # umount /tmp/usbkey
180
181 Install the boot device in the target board and configure the BIOS to boot
182 from it.
183
184 For more details on the USB-ZIP scenario, see the syslinux documentation:
185 http://git.kernel.org/?p=boot/syslinux/syslinux.git;a=blob_plain;f=doc/usbkey.txt;hb=HEAD
186 138
187 139
188Texas Instruments Beaglebone (beaglebone) 140Texas Instruments Beaglebone (beaglebone)