diff options
Diffstat (limited to 'meta-isg/meta-haswell-wc/README')
-rw-r--r-- | meta-isg/meta-haswell-wc/README | 172 |
1 files changed, 0 insertions, 172 deletions
diff --git a/meta-isg/meta-haswell-wc/README b/meta-isg/meta-haswell-wc/README deleted file mode 100644 index 2b7f2753..00000000 --- a/meta-isg/meta-haswell-wc/README +++ /dev/null | |||
@@ -1,172 +0,0 @@ | |||
1 | This README file contains information on building the meta-haswell-wc | ||
2 | BSP layer, and booting the images contained in the /binary directory. | ||
3 | Please see the corresponding sections below for details. | ||
4 | |||
5 | The BSP is made specifically for 4th Gen Intel Core Processor (Haswell) | ||
6 | Development Kit with Mobile Intel QM87 & HM86 Chipset (formerly known as | ||
7 | Shark Bay). This BSP assumes that integrated graphics are being used. | ||
8 | The "haswell-wc" BSP is meant to support "Walnut Canyon" Shark Bay | ||
9 | development kit. | ||
10 | |||
11 | Further information about the Haswell Platforms supported by this BSP can be | ||
12 | found here: | ||
13 | |||
14 | http://www.intel.com/content/www/us/en/intelligent-systems/shark-bay/4th-generation-core-qm87-hm86-chipsets.html | ||
15 | |||
16 | Information on all IntelĀ® embedded platforms can be found here: | ||
17 | |||
18 | http://www.intel.com/p/en_US/embedded/hwsw/hardware | ||
19 | |||
20 | |||
21 | Compliance | ||
22 | ========== | ||
23 | |||
24 | This BSP is compliant with the Yocto Project as per the requirements | ||
25 | listed here: | ||
26 | |||
27 | https://www.yoctoproject.org/webform/yocto-project-compatible-registration | ||
28 | |||
29 | |||
30 | Dependencies | ||
31 | ============ | ||
32 | |||
33 | This layer depends on: | ||
34 | |||
35 | URI: git://git.openembedded.org/bitbake | ||
36 | branch: master | ||
37 | |||
38 | URI: git://git.openembedded.org/openembedded-core | ||
39 | layers: meta | ||
40 | branch: master | ||
41 | |||
42 | URI: git://git.yoctoproject.org/meta-intel | ||
43 | layers: intel | ||
44 | branch: master | ||
45 | |||
46 | Patches | ||
47 | ======= | ||
48 | |||
49 | Please submit any patches against this BSP to the Yocto mailing list | ||
50 | (meta-intel@yoctoproject.org) and cc: the maintainer: | ||
51 | |||
52 | Maintainer: Ng Wei Tee <wei.tee.ng@intel.com> | ||
53 | |||
54 | Please see the meta-intel/MAINTAINERS file for more details. | ||
55 | |||
56 | |||
57 | Table of Contents | ||
58 | ================= | ||
59 | |||
60 | I. Building the meta-haswell-wc BSP layer | ||
61 | II. Booting the images in /binary | ||
62 | III. Device Notes | ||
63 | a. Boot Loader | ||
64 | b. I/O drivers | ||
65 | |||
66 | |||
67 | I. Building the meta-haswell-wc BSP layer | ||
68 | ======================================= | ||
69 | |||
70 | In order to build an image with BSP support for a given release, you | ||
71 | need to download the corresponding BSP tarball from the 'Board Support | ||
72 | Package (BSP) Downloads' page of the Yocto Project website. | ||
73 | |||
74 | Having done that, and assuming you extracted the BSP tarball contents | ||
75 | at the top-level of your yocto build tree, you can build a haswell-wc | ||
76 | image by adding the location of the meta-haswell-wc layer to | ||
77 | bblayers.conf, along with the meta-intel layer itself (to access | ||
78 | common metadata shared between BSPs) e.g.: | ||
79 | |||
80 | yocto/meta-intel \ | ||
81 | yocto/meta-intel/meta-isg/meta-haswell-wc \ | ||
82 | |||
83 | To enable the haswell-wc layer, add the haswell-wc MACHINE to local.conf: | ||
84 | |||
85 | MACHINE ?= "haswell-wc" | ||
86 | |||
87 | You should then be able to build a haswell-wc image as such: | ||
88 | |||
89 | $ source oe-init-build-env | ||
90 | $ bitbake core-image-sato | ||
91 | |||
92 | At the end of a successful build, you should have a live image that | ||
93 | you can boot from a USB flash drive (see instructions on how to do | ||
94 | that below, in the section 'Booting the images from /binary'). | ||
95 | |||
96 | NOTE: The 'haswell-wc' machine will include support for hardware video | ||
97 | acceleration via gstreamer if and only if the "commercial" string is | ||
98 | added to the the LICENSE_FLAGS_WHITELIST variable in your local.conf. | ||
99 | |||
100 | For example: | ||
101 | |||
102 | LICENSE_FLAGS_WHITELIST = "commercial" | ||
103 | |||
104 | The reason this is needed is to prevent the image from including | ||
105 | anything that might violate the license terms of the packages used to | ||
106 | implement the the video acceleration feature, such as gst-ffmpeg and | ||
107 | ffmpeg. As always, please consult the licenses included in the | ||
108 | specific packages for details if you use packages that require | ||
109 | particular LICENSE_FLAGS. | ||
110 | |||
111 | As an alternative to downloading the BSP tarball, you can also work | ||
112 | directly from the meta-intel git repository. For each BSP in the | ||
113 | 'meta-intel' repository, there are multiple branches, one | ||
114 | corresponding to each major release starting with 'laverne' (0.90), in | ||
115 | addition to the latest code which tracks the current master (note that | ||
116 | not all BSPs are present in every release). Instead of extracting a | ||
117 | BSP tarball at the top level of your yocto build tree, you can | ||
118 | equivalently check out the appropriate branch from the meta-intel | ||
119 | repository at the same location. | ||
120 | |||
121 | |||
122 | II. Booting the images in /binary | ||
123 | ================================= | ||
124 | |||
125 | This BSP contains bootable live images, which can be used to directly | ||
126 | boot Yocto off of a USB flash drive. | ||
127 | |||
128 | Under Linux, insert a USB flash drive. Assuming the USB flash drive | ||
129 | takes device /dev/sdf, use dd to copy the live image to it. For | ||
130 | example: | ||
131 | |||
132 | # dd if=core-image-sato-haswell-wc.hddimg of=/dev/sdf | ||
133 | # sync | ||
134 | # eject /dev/sdf | ||
135 | |||
136 | This should give you a bootable USB flash device. Insert the device | ||
137 | into a bootable USB socket on the target, and power on. This should | ||
138 | result in a system booted to the Sato graphical desktop. | ||
139 | |||
140 | If you want a terminal, use the arrows at the top of the UI to move to | ||
141 | different pages of available applications, one of which is named | ||
142 | 'Terminal'. Clicking that should give you a root terminal. | ||
143 | |||
144 | If you want to ssh into the system, you can use the root terminal to | ||
145 | ifconfig the IP address and use that to ssh in. The root password is | ||
146 | empty, so to log in type 'root' for the user name and hit 'Enter' at | ||
147 | the Password prompt: and you should be in. | ||
148 | |||
149 | ---- | ||
150 | |||
151 | If you find you're getting corrupt images on the USB (it doesn't show | ||
152 | the syslinux boot: prompt, or the boot: prompt contains strange | ||
153 | characters), try doing this first: | ||
154 | |||
155 | # dd if=/dev/zero of=/dev/sdf bs=1M count=512 | ||
156 | |||
157 | |||
158 | III. Device Notes | ||
159 | ================= | ||
160 | |||
161 | a. Boot Loader | ||
162 | -------------- | ||
163 | BIOS: HSWLPTU1.86C.0131.R05.1308140140 | ||
164 | |||
165 | b. I/O drivers | ||
166 | -------------- | ||
167 | Support integrated graphics driver (i965) | ||
168 | |||
169 | Support SATA, USB Host v2.0 | ||
170 | |||
171 | Supported I/O devices (APIC, RTC, SPI, UART, I2C, LPS, SMBus i801, | ||
172 | WDT, and HPET) | ||