summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorTom Zanussi <tom.zanussi@intel.com>2011-08-26 03:26:18 (GMT)
committerTom Zanussi <tom.zanussi@intel.com>2011-08-26 03:26:18 (GMT)
commitb3cf3a9825bbe81179632b88635fa8f3eb07018c (patch)
treed8989a1dc8342ea634874fd5411c91a83b4c9d35
parent3f002cdb9a6bc991fead405ed45338c42b93108d (diff)
downloadmeta-intel-b3cf3a9825bbe81179632b88635fa8f3eb07018c.tar.gz
meta-crownbay: update README
With the new emgd-driver-bin recipe, some of the extensive instructions on how to manually download and set up EMGD for the build are no longer necessary. Changes to reflect the new image names and a couple other minor cleanups are also included. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
-rw-r--r--meta-crownbay/README181
1 files changed, 31 insertions, 150 deletions
diff --git a/meta-crownbay/README b/meta-crownbay/README
index 89056ed..439b8c7 100644
--- a/meta-crownbay/README
+++ b/meta-crownbay/README
@@ -6,7 +6,7 @@ The Crown Bay platform consists of the Intel Atom Z6xx processor,
6plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff). 6plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff).
7 7
8It also supports the E6xx embedded on-chip graphics via the Intel 8It also supports the E6xx embedded on-chip graphics via the Intel
9Embedded Media and Graphics Driver (EMGD) 1.6 Gold Driver. 9Embedded Media and Graphics Driver (EMGD) 1.8 Driver.
10 10
11Table of Contents 11Table of Contents
12================= 12=================
@@ -33,10 +33,10 @@ bblayers.conf e.g.:
33The meta-crownbay layer contains support for two different machine 33The meta-crownbay layer contains support for two different machine
34configurations. These configurations are identical except for the fact 34configurations. These configurations are identical except for the fact
35that the one prefixed with 'crownbay' makes use of the 35that the one prefixed with 'crownbay' makes use of the
36Intel-proprietary EMGD 1.6 graphics driver, while the one prefixed 36Intel-proprietary EMGD 1.8 graphics driver, while the one prefixed
37with 'crownbay-noemgd' does not. 37with 'crownbay-noemgd' does not.
38 38
39If you want to enable the layer that supports EMGD graphics add 39If you want to enable the layer that supports EMGD graphics add the
40following to the local.conf file: 40following to the local.conf file:
41 41
42 MACHINE ?= "crownbay" 42 MACHINE ?= "crownbay"
@@ -48,8 +48,8 @@ add the following to the local.conf file:
48 48
49You should then be able to build a crownbay image as such: 49You should then be able to build a crownbay image as such:
50 50
51 $ source poky-init-build-env 51 $ source oe-init-build-env
52 $ bitbake poky-image-sato-live 52 $ bitbake core-image-sato
53 53
54At the end of a successful build, you should have a live image that 54At the end of a successful build, you should have a live image that
55you can boot from a USB flash drive (see instructions on how to do 55you can boot from a USB flash drive (see instructions on how to do
@@ -59,10 +59,11 @@ As an alternative to downloading the BSP tarball, you can also work
59directly from the meta-intel git repository. For each BSP in the 59directly from the meta-intel git repository. For each BSP in the
60'meta-intel' repository, there are multiple branches, one 60'meta-intel' repository, there are multiple branches, one
61corresponding to each major release starting with 'laverne' (0.90), in 61corresponding to each major release starting with 'laverne' (0.90), in
62addition to the latest code which tracks the current master. Instead 62addition to the latest code which tracks the current master (note that
63of extracting a BSP tarball at the top level of your yocto build tree, 63not all BSPs are present in every release). Instead of extracting
64you can equivalently check out the appropriate branch from the 64a BSP tarball at the top level of your yocto build tree, you can
65meta-intel repository at the same location. 65equivalently check out the appropriate branch from the meta-intel
66repository at the same location.
66 67
67 68
68II. Special notes for building the meta-crownbay BSP layer 69II. Special notes for building the meta-crownbay BSP layer
@@ -73,39 +74,33 @@ userspace drivers when building the "crownbay" machine (but not when
73building the "crownbay-noemgd" machine). If you got the BSP from the 74building the "crownbay-noemgd" machine). If you got the BSP from the
74'BSP Downloads' section of the Yocto website, the EMGD binaries needed 75'BSP Downloads' section of the Yocto website, the EMGD binaries needed
75to perform the build will already be present in the BSP, located in 76to perform the build will already be present in the BSP, located in
76the recipes-graphics/xorg-xserver/emgd-driver-bin-1.6 directory, and 77the meta-intel/common/recipes-graphics/xorg-xserver/emgd-driver-bin-1.8
77you can ignore the rest of this section. 78directory, and you can ignore the rest of this section.
78 79
79If you didn't get the BSP from the 'BSP Downloads' section of the 80If you didn't get the BSP from the 'BSP Downloads' section of the
80Yocto website, you have two choices: 81Yocto website, you can download a tarball containing an rpm that
82contains the binaries and extract the binaries from that, and copy
83them to the proper location in the meta-crownbay layer.
81 84
82- You can download a tarball containing an rpm that contains the 85The following subsection describes that process in detail.
83 binaries and extract the binaries from that, and copy them to the
84 proper location in the meta-crownbay layer.
85 86
86- You can download a Windows executable from the official EMGD
87 website, extract the binaries from it, and copy them to the proper
88 location in the meta-crownbay layer.
89 87
90The following subsections describe each option in detail. 88Downloading and extracting the binaries using the EMGD Linux tarball
89--------------------------------------------------------------------
91 90
92 91The first step of the process is to download the EMGD 1.8 Driver.
93IIa Downloading and extracting the binaries using the EMGD Linux tarball 92Here is the current link to the URL from which it can be downloaded:
94------------------------------------------------------------------------
95
96The first step of the process is to download the EMGD 1.6 Gold Driver.
97Here is the current link to the URL which it can be downloaded from:
98 93
99http://edc.intel.com/Software/Downloads/EMGD/ 94http://edc.intel.com/Software/Downloads/EMGD/
100 95
101In the Download Now tab, select: 96In the Download Now tab, select:
102 97
103Intel® architecture-based product: Linux Tar Ball 98Intel® architecture-based product: Linux Tar Ball
104Operating System: MeeGo 1.0 IVI Linux (kernel 2.6.33.3, X.server 1.8.0) 99Operating System: MeeGo* 1.2 IVI Linux* (kernel 2.6.37, X.server 1.9, Mesa 7.9)
105 100
106That will give you a large tar file: 101That will give you a large .tgz file:
107 102
108Lin_EMGD_1_6_RC_1922.tar 103Lin_EMGD_1_8_RC_2032.tgz
109 104
110Extract the files in the tar file, which will in turn give you a 105Extract the files in the tar file, which will in turn give you a
111directory named IEMGD_HEAD_Linux. 106directory named IEMGD_HEAD_Linux.
@@ -114,138 +109,24 @@ The binaries are contained in an rpm file; you can extract the
114binaries from the rpm file using rpm2cpio and cpio: 109binaries from the rpm file using rpm2cpio and cpio:
115 110
116$ cd IEMGD_HEAD_Linux/MeeGo1.2 111$ cd IEMGD_HEAD_Linux/MeeGo1.2
117$ rpm2cpio emgd-bin-1922-1.6.i586.rpm > emgd-bin-1922-1.6.i586.cpio 112$ rpm2cpio emgd-bin-2032-1.6.i586.rpm > emgd-bin-2032-1.6.i586.cpio
118$ mkdir extracted; cd extracted 113$ mkdir extracted; cd extracted
119$ cpio -idv < ../poky-image-minimal-initramfs-emenlow.cpio 114$ cpio -idv < ../emgd-bin-2032-1.6.i586.cpio
120 115
121Finally, you can copy the xorg-xserver binaries to the 116Finally, you can copy the xorg-xserver binaries to the
122emgd-driver-bin-1.6 directory in the meta-crownbay layer: 117emgd-driver-bin-1.8 directory in meta-intel/common:
123 118
124$ cp -a usr/lib meta-crownbay/recipes-graphics/xorg-xserver/emgd-driver-bin-1.6 119$ cp -a usr/lib meta-intel/common/recipes-graphics/xorg-xserver/emgd-driver-bin-1.8
125 120
126You also need to copy the IEMGD License.txt file to the same directory: 121You also need to copy the IEMGD License.txt file to the same directory:
127 122
128$ cp IEMGD_HEAD_Linux/License/License.txt meta-crownbay/recipes/xorg-xserver/emgd-driver-bin-1.6 123$ cp IEMGD_HEAD_Linux/License/License.txt meta-intel/common/recipes/xorg-xserver/emgd-driver-bin-1.8
129 124
130At this point, you should be able to build meta-crownbay images as usual. 125At this point, you should be able to build meta-crownbay images as usual.
131 126
132 127
133IIb Extracting the binaries using the graphical ced application 128III. Booting the images in /binary
134--------------------------------------------------------------- 129==================================
135
136These steps require that you run a graphical application in Windows.
137Windows 7 was used for these instructions, but it shouldn't matter
138which version of Windows you use.
139
140The first step of the process is to download the EMGD 1.6 Gold Driver.
141Here is the current link to the URL which it can be downloaded from:
142
143http://edc.intel.com/Software/Downloads/EMGD/
144
145In the Download Now tab, select:
146
147Intel® architecture-based product: Intel Atom Processor E6XX Series
148Operating System: MeeGo 1.0 IVI Linux (kernel 2.6.33.3, X.server 1.8.0)
149
150That will give you a large zip file:
151
152IEMGD_1_6_GOLD_1922.zip
153
154Extract the files in the zip file, which will in turn give you a large
155.exe file:
156
157IEMGD_1_6_GOLD_ALL_1922.exe
158
159Run IEMGD_1_6_GOLD_ALL_1922.exe to install, accept licenses, etc.
160
161If it says to install watcom, follow the instructions to do that.
162
163When the installation completes, an application named "emgd-ced" will
164be present in the install directory. Double-click to run it.
165
166Select the menu item: New Configuration
167
168In the tabbed page, make the following selections and/or enter the
169specified data:
170
171Configuration File Name: myconfig
172Platform Chipset: Intel Atom Processor E6xx
173Port Devices: LVDS, sDVO
174
175Hit the 'Next' button.
176
177On the next tabbed page, make the following selections and/or enter
178the specified data:
179
180Readable Port Name: portname0
181Encoder Configuration: Select sDVO Device: Internal LVDS
182
183Hit the 'Finish' button.
184
185Select the menu item: New Package
186
187In the tabbed page, make the following selections and/or enter the
188specified data:
189
190Package File Name: mypackage
191Configurations: selec myconfig.cnfg
192Target OS: Linux operating System
193
194Hit the 'Finish' button.
195
196Select the menu item: Generate Installation
197
198This will create the EMGD installation package:
199
200Generating EMGD installation...
201
202The installation package should now be under the 'workspace'
203subdirectory of the directory you installed to:
204
205workspace/installation/mypackage.pkg_installation/IEMGD_HEAD_Linux/IEMGD_HEAD_Linux.tgz
206
207This is the file you are interested in. Copy it to your Poky build
208system, and uncompress/untar it:
209
210$ tar cvfz IEMGD_HEAD_Linux.tgz
211
212The binaries are contained in an rpm file; you can extract the
213binaries from the rpm file using rpm2cpio and cpio:
214
215$ cd IEMGD_HEAD_Linux/MeeGo1.2
216$ rpm2cpio emgd-bin-1922-1.6.i586.rpm > emgd-bin-1922-1.6.i586.cpio
217$ mkdir extracted; cd extracted
218$ cpio -idv < ../poky-image-minimal-initramfs-emenlow.cpio
219
220Finally, you can copy the xorg-xserver binaries to the
221emgd-driver-bin-1.6 directory in the meta-crownbay layer:
222
223$ cp -a usr/lib meta-crownbay/recipes-graphics/xorg-xserver/emgd-driver-bin-1.6
224
225You also need to copy the IEMGD License.txt file to the same directory:
226
227$ cp IEMGD_HEAD_Linux/License/License.txt meta-crownbay/recipes/xorg-xserver/emgd-driver-bin-1.6
228
229At this point, you should be able to build meta-crownbay images as usual.
230
231----
232
233For reference, the EMGD Driver documentation is also available at the
234above link.
235
236The specific text of the document is:
237
238User Guide: Intel® Embedded Media and Graphics Driver, EFI Video
239Driver, EPOG, and Video BIOS v1.6 for Windows* XP and Linux* Provides
240installation requirements/procedures & describes the vbios/firmware,
241configuration options, & functionality of Intel® EMGD under Windows* &
242Linux*. Refer to guide for details.
243
244April 2011
245
246
247II. Booting the images in /binary
248=================================
249 130
250This BSP contains bootable live images, which can be used to directly 131This BSP contains bootable live images, which can be used to directly
251boot Yocto off of a USB flash drive. 132boot Yocto off of a USB flash drive.
@@ -254,7 +135,7 @@ Under Linux, insert a USB flash drive. Assuming the USB flash drive
254takes device /dev/sdf, use dd to copy the live image to it. For 135takes device /dev/sdf, use dd to copy the live image to it. For
255example: 136example:
256 137
257# dd if=poky-image-sato-live-crownbay-20101207053738.hddimg of=/dev/sdf 138# dd if=core-image-sato-crownbay-20101207053738.hddimg of=/dev/sdf
258# sync 139# sync
259# eject /dev/sdf 140# eject /dev/sdf
260 141