diff options
Diffstat (limited to 'README')
-rw-r--r-- | README | 73 |
1 files changed, 10 insertions, 63 deletions
@@ -33,9 +33,8 @@ Table of Contents | |||
33 | 33 | ||
34 | I. Overview | 34 | I. Overview |
35 | II. Building and booting meta-intel BSP layers | 35 | II. Building and booting meta-intel BSP layers |
36 | a. Building the intel-common and quark BSP layers | 36 | a. Building the intel-common BSP layers |
37 | b. Booting the intel-common BSP images | 37 | b. Booting the intel-common BSP images |
38 | c. Booting the intel-quark BSP image on a Galileo board | ||
39 | III. Technical Miscellany | 38 | III. Technical Miscellany |
40 | Benefits of using meta-intel | 39 | Benefits of using meta-intel |
41 | The intel-common kernel package architecture | 40 | The intel-common kernel package architecture |
@@ -49,8 +48,7 @@ I. Overview | |||
49 | 48 | ||
50 | This is the location for Intel-maintained BSPs. | 49 | This is the location for Intel-maintained BSPs. |
51 | 50 | ||
52 | For details on the intel-common and intel-quark BSPs, see the | 51 | For details on the intel-common, see the information below. |
53 | information below. | ||
54 | 52 | ||
55 | For all others, please see the README files contained in the | 53 | For all others, please see the README files contained in the |
56 | individual BSP layers for BSP-specific information. | 54 | individual BSP layers for BSP-specific information. |
@@ -87,24 +85,22 @@ II. Building and booting meta-intel BSP layers | |||
87 | The following sections contain information on building and booting the | 85 | The following sections contain information on building and booting the |
88 | BSPs contained in the meta-intel layer. | 86 | BSPs contained in the meta-intel layer. |
89 | 87 | ||
90 | Note that these instructions specifically cover the intel-common and | 88 | Note that these instructions specifically cover the intel-common, which |
91 | quark BSPs, which may or may not be applicable to other BSPs contained | 89 | may or may not be applicable to other BSPs contained in this layer - if |
92 | in this layer - if a given BSP contains its own README, that version | 90 | a given BSP contains its own README, that version should be used instead, |
93 | should be used instead, and these instructions can be ignored. | 91 | and these instructions can be ignored. |
94 | 92 | ||
95 | a. Building the intel-common and quark BSP layers | 93 | a. Building the intel-common BSP layers |
96 | ------------------------------------------------- | 94 | ------------------------------------------------- |
97 | 95 | ||
98 | In order to build an image with BSP support for a given release, you | 96 | In order to build an image with BSP support for a given release, you |
99 | need to download the corresponding BSP tarball from the 'Board Support | 97 | need to download the corresponding BSP tarball from the 'Board Support |
100 | Package (BSP) Downloads' page of the Yocto Project website (or | 98 | Package (BSP) Downloads' page of the Yocto Project website (or |
101 | equivalently, check out the appropriate branch from the meta-intel git | 99 | equivalently, check out the appropriate branch from the meta-intel git |
102 | repository, see below). For the intel-common and quark BSPs, those | 100 | repository, see below). For the intel-common BSPs, those tarballs would |
103 | tarballs would correspond to the following choices in the BSP | 101 | correspond to the following choices in the BSP downloads section: |
104 | downloads section: | ||
105 | 102 | ||
106 | - Intel-core2-32 Intel® Common Core BSP (Intel-core2-32) | 103 | - Intel-core2-32 Intel® Common Core BSP (Intel-core2-32) |
107 | - Intel-core2-32 Intel® Common Core BSP (Intel-quark) | ||
108 | - Intel-corei7-64 Intel® Common Core BSP (Intel-corei7-64) | 104 | - Intel-corei7-64 Intel® Common Core BSP (Intel-corei7-64) |
109 | 105 | ||
110 | The intel-* BSPs, also known as the intel-common BSPs, provide a few | 106 | The intel-* BSPs, also known as the intel-common BSPs, provide a few |
@@ -137,10 +133,6 @@ where 'xxx' is replaced by one of the following BSP names: | |||
137 | This BSP is optimized for Nehalem and later Core and Xeon CPUs as | 133 | This BSP is optimized for Nehalem and later Core and Xeon CPUs as |
138 | well as Silvermont and later Atom CPUs, such as the Baytrail SoCs. | 134 | well as Silvermont and later Atom CPUs, such as the Baytrail SoCs. |
139 | 135 | ||
140 | - intel-quark | ||
141 | |||
142 | This BSP is optimized for Quark-based systems. | ||
143 | |||
144 | You should then be able to build an image as such: | 136 | You should then be able to build an image as such: |
145 | 137 | ||
146 | $ source oe-init-build-env | 138 | $ source oe-init-build-env |
@@ -198,45 +190,6 @@ characters), try doing this first: | |||
198 | 190 | ||
199 | $ dd if=/dev/zero of=/dev/sdf bs=1M count=512 | 191 | $ dd if=/dev/zero of=/dev/sdf bs=1M count=512 |
200 | 192 | ||
201 | c. Booting the intel-quark BSP image on a Galileo board | ||
202 | ------------------------------------------------------- | ||
203 | |||
204 | If you downloaded the BSP tarball, you will find bootable images in | ||
205 | the /binary directory. If you've built your own image, either from | ||
206 | the downloaded BSP layer or from the meta-intel git repository, you'll | ||
207 | find the bootable image in the build/tmp/deploy/images/xxx directory, | ||
208 | where again 'xxx' refers to the machine name used in the build. | ||
209 | |||
210 | The Galileo board can boot off of either an SD card or USB storage | ||
211 | media that has a special disk layout. The 'wic' tool can be used to | ||
212 | create directly bootable images for either of the two formats via the | ||
213 | following steps. As of meta-intel 6.0-morty-2.2 or newer, wic images are | ||
214 | created automatically during build time, and the manual use of wic is | ||
215 | not necessary. By default, the galileodisk-sd wic kickstart file is used, | ||
216 | which targets SD cards. This can be changed by setting the WKS_FILE to | ||
217 | something else in local.conf, such as the following: | ||
218 | |||
219 | WKS_FILE = “galileodisk-usb” | ||
220 | |||
221 | If your build is successful, a .wic image will be created in the usual | ||
222 | deploy directory. Write this image to an SD card: | ||
223 | |||
224 | $ sudo dd if=/path/to/image/image-name.wic of=/dev/your_sd_dev | ||
225 | $ sync | ||
226 | $ sudo eject /dev/your_sd_dev | ||
227 | |||
228 | Insert the SD card into the Galileo and power on. | ||
229 | |||
230 | The Galileo board can boot from an hddimg formatted USB drive as well, | ||
231 | but currently only live-boot, and not installation, is supported. | ||
232 | An image in hddimg format is generated when you build the quark BSP. | ||
233 | You can follow the procedure in II.b to use dd command to prepare your USB | ||
234 | drive, then press F7 key during startup to bring up the boot option menu. | ||
235 | Choose the UEFI USB boot option for the drive to boot the system. If the board | ||
236 | already passes this stage and show a grub boot menu, you can press 'c' | ||
237 | key and then type "quit" in grub shell. The board should come back to | ||
238 | the UEFI boot menu. | ||
239 | |||
240 | III. Technical Miscellany | 193 | III. Technical Miscellany |
241 | ========================= | 194 | ========================= |
242 | 195 | ||
@@ -251,9 +204,7 @@ intel-* MACHINEs each have different compilation flags appropriate for their | |||
251 | targeted hardware sets. intel-corei7-64 has tune flags appropriate for modern | 204 | targeted hardware sets. intel-corei7-64 has tune flags appropriate for modern |
252 | 64-bit Intel Core i microarchitecture, and includes instruction sets up to | 205 | 64-bit Intel Core i microarchitecture, and includes instruction sets up to |
253 | SSE4.2. intel-core2-32 has tune flags appropriate for legacy 32-bit Intel Core2 | 206 | SSE4.2. intel-core2-32 has tune flags appropriate for legacy 32-bit Intel Core2 |
254 | microarchitecture, and includes instruction sets up to SSE3. intel-quark | 207 | microarchitecture, and includes instruction sets up to SSE3. |
255 | contains a subset of the intel-core2-32 instruction set, as quark does not | ||
256 | support prefix locking instructions. | ||
257 | 208 | ||
258 | linux-intel kernel | 209 | linux-intel kernel |
259 | ++++++++++++++++++ | 210 | ++++++++++++++++++ |
@@ -415,14 +366,10 @@ Turbot, so it is tested against both intel-corei7-64 and intel-core2-32. | |||
415 | intel-corei7-64: | 366 | intel-corei7-64: |
416 | NUC6i5SYH | 367 | NUC6i5SYH |
417 | MinnowBoard Turbot | 368 | MinnowBoard Turbot |
418 | Braswell RVP | ||
419 | 369 | ||
420 | intel-core2-32: | 370 | intel-core2-32: |
421 | MinnowBoard Turbot | 371 | MinnowBoard Turbot |
422 | 372 | ||
423 | Intel-quark: | ||
424 | Galileo 2 | ||
425 | |||
426 | 373 | ||
427 | V. Guidelines for submitting patches | 374 | V. Guidelines for submitting patches |
428 | ==================================== | 375 | ==================================== |