summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorSaul Wold <sgw@linux.intel.com>2017-12-08 14:54:16 (GMT)
committerCalifornia Sullivan <california.l.sullivan@intel.com>2017-12-08 23:04:46 (GMT)
commit6f988495c3f560ee3b639ad986e67e531cceb91f (patch)
tree47127f8446c0d3b6de47996569603a029d682d13 /README
parent5dbc69e339588834317b632119717996584b0d6c (diff)
downloadmeta-intel-6f988495c3f560ee3b639ad986e67e531cceb91f.tar.gz
README: Remove Quark references
Signed-off-by: Saul Wold <sgw@linux.intel.com> Signed-off-by: California Sullivan <california.l.sullivan@intel.com>
Diffstat (limited to 'README')
-rw-r--r--README73
1 files changed, 10 insertions, 63 deletions
diff --git a/README b/README
index d16f692..87e7de3 100644
--- a/README
+++ b/README
@@ -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
50This is the location for Intel-maintained BSPs. 49This is the location for Intel-maintained BSPs.
51 50
52For details on the intel-common and intel-quark BSPs, see the 51For details on the intel-common, see the information below.
53information below.
54 52
55For all others, please see the README files contained in the 53For all others, please see the README files contained in the
56individual BSP layers for BSP-specific information. 54individual BSP layers for BSP-specific information.
@@ -87,24 +85,22 @@ II. Building and booting meta-intel BSP layers
87The following sections contain information on building and booting the 85The following sections contain information on building and booting the
88BSPs contained in the meta-intel layer. 86BSPs contained in the meta-intel layer.
89 87
90Note that these instructions specifically cover the intel-common and 88Note that these instructions specifically cover the intel-common, which
91quark BSPs, which may or may not be applicable to other BSPs contained 89may or may not be applicable to other BSPs contained in this layer - if
92in this layer - if a given BSP contains its own README, that version 90a given BSP contains its own README, that version should be used instead,
93should be used instead, and these instructions can be ignored. 91and these instructions can be ignored.
94 92
95a. Building the intel-common and quark BSP layers 93a. Building the intel-common BSP layers
96------------------------------------------------- 94-------------------------------------------------
97 95
98In order to build an image with BSP support for a given release, you 96In order to build an image with BSP support for a given release, you
99need to download the corresponding BSP tarball from the 'Board Support 97need to download the corresponding BSP tarball from the 'Board Support
100Package (BSP) Downloads' page of the Yocto Project website (or 98Package (BSP) Downloads' page of the Yocto Project website (or
101equivalently, check out the appropriate branch from the meta-intel git 99equivalently, check out the appropriate branch from the meta-intel git
102repository, see below). For the intel-common and quark BSPs, those 100repository, see below). For the intel-common BSPs, those tarballs would
103tarballs would correspond to the following choices in the BSP 101correspond to the following choices in the BSP downloads section:
104downloads 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
110The intel-* BSPs, also known as the intel-common BSPs, provide a few 106The 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
144You should then be able to build an image as such: 136You 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
201c. Booting the intel-quark BSP image on a Galileo board
202-------------------------------------------------------
203
204If you downloaded the BSP tarball, you will find bootable images in
205the /binary directory. If you've built your own image, either from
206the downloaded BSP layer or from the meta-intel git repository, you'll
207find the bootable image in the build/tmp/deploy/images/xxx directory,
208where again 'xxx' refers to the machine name used in the build.
209
210The Galileo board can boot off of either an SD card or USB storage
211media that has a special disk layout. The 'wic' tool can be used to
212create directly bootable images for either of the two formats via the
213following steps. As of meta-intel 6.0-morty-2.2 or newer, wic images are
214created automatically during build time, and the manual use of wic is
215not necessary. By default, the galileodisk-sd wic kickstart file is used,
216which targets SD cards. This can be changed by setting the WKS_FILE to
217something else in local.conf, such as the following:
218
219WKS_FILE = “galileodisk-usb”
220
221If your build is successful, a .wic image will be created in the usual
222deploy 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
228Insert the SD card into the Galileo and power on.
229
230The Galileo board can boot from an hddimg formatted USB drive as well,
231but currently only live-boot, and not installation, is supported.
232An image in hddimg format is generated when you build the quark BSP.
233You can follow the procedure in II.b to use dd command to prepare your USB
234drive, then press F7 key during startup to bring up the boot option menu.
235Choose the UEFI USB boot option for the drive to boot the system. If the board
236already passes this stage and show a grub boot menu, you can press 'c'
237key and then type "quit" in grub shell. The board should come back to
238the UEFI boot menu.
239
240III. Technical Miscellany 193III. Technical Miscellany
241========================= 194=========================
242 195
@@ -251,9 +204,7 @@ intel-* MACHINEs each have different compilation flags appropriate for their
251targeted hardware sets. intel-corei7-64 has tune flags appropriate for modern 204targeted hardware sets. intel-corei7-64 has tune flags appropriate for modern
25264-bit Intel Core i microarchitecture, and includes instruction sets up to 20564-bit Intel Core i microarchitecture, and includes instruction sets up to
253SSE4.2. intel-core2-32 has tune flags appropriate for legacy 32-bit Intel Core2 206SSE4.2. intel-core2-32 has tune flags appropriate for legacy 32-bit Intel Core2
254microarchitecture, and includes instruction sets up to SSE3. intel-quark 207microarchitecture, and includes instruction sets up to SSE3.
255contains a subset of the intel-core2-32 instruction set, as quark does not
256support prefix locking instructions.
257 208
258linux-intel kernel 209linux-intel kernel
259++++++++++++++++++ 210++++++++++++++++++
@@ -415,14 +366,10 @@ Turbot, so it is tested against both intel-corei7-64 and intel-core2-32.
415intel-corei7-64: 366intel-corei7-64:
416 NUC6i5SYH 367 NUC6i5SYH
417 MinnowBoard Turbot 368 MinnowBoard Turbot
418 Braswell RVP
419 369
420intel-core2-32: 370intel-core2-32:
421 MinnowBoard Turbot 371 MinnowBoard Turbot
422 372
423Intel-quark:
424 Galileo 2
425
426 373
427V. Guidelines for submitting patches 374V. Guidelines for submitting patches
428==================================== 375====================================