summaryrefslogtreecommitdiffstats
path: root/meta-crownbay
diff options
context:
space:
mode:
authorTom Zanussi <tom.zanussi@intel.com>2012-01-24 17:40:29 (GMT)
committerTom Zanussi <tom.zanussi@intel.com>2012-01-30 20:58:54 (GMT)
commitfd14750345ef7e4a543b9da18000de9a18e3439a (patch)
tree7d776c3c806476fd1c7095af59a1030edec8a043 /meta-crownbay
parent67eb15383345a3f88ad3d744a0650cb3d2753998 (diff)
downloadmeta-intel-fd14750345ef7e4a543b9da18000de9a18e3439a.tar.gz
meta-crownbay: update README
The new emgd-driver-bin_1.10 recipe no longer requires manually extracting and installing emgd binaries, so remove the section that deals with that. It does require a new LICENSE_FLAGS_WHITELIST entry in local.conf, so add instructions detailing that. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Diffstat (limited to 'meta-crownbay')
-rw-r--r--meta-crownbay/README97
1 files changed, 12 insertions, 85 deletions
diff --git a/meta-crownbay/README b/meta-crownbay/README
index 65289f7..b56c79a 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.8 Driver. 9Embedded Media and Graphics Driver (EMGD) 1.10 Driver.
10 10
11 11
12Dependencies 12Dependencies
@@ -41,8 +41,7 @@ Table of Contents
41================= 41=================
42 42
43 I. Building the meta-crownbay BSP layer 43 I. Building the meta-crownbay BSP layer
44 II. Special notes for building the meta-crownbay BSP layer 44 II. Booting the images in /binary
45III. Booting the images in /binary
46 45
47 46
48I. Building the meta-crownbay BSP layer 47I. Building the meta-crownbay BSP layer
@@ -64,7 +63,7 @@ common metadata shared between BSPs) e.g.:
64The meta-crownbay layer contains support for two different machine 63The meta-crownbay layer contains support for two different machine
65configurations. These configurations are identical except for the fact 64configurations. These configurations are identical except for the fact
66that the one prefixed with 'crownbay' makes use of the 65that the one prefixed with 'crownbay' makes use of the
67Intel-proprietary EMGD 1.8 graphics driver, while the one prefixed 66Intel-proprietary EMGD 1.10 graphics driver, while the one prefixed
68with 'crownbay-noemgd' does not. 67with 'crownbay-noemgd' does not.
69 68
70If you want to enable the layer that supports EMGD graphics add the 69If you want to enable the layer that supports EMGD graphics add the
@@ -72,6 +71,13 @@ following to the local.conf file:
72 71
73 MACHINE ?= "crownbay" 72 MACHINE ?= "crownbay"
74 73
74The 'crownbay' machine includes the emgd-driver-bin package, which has
75a proprietary license that must be whitelisted by adding the string
76"license_emgd-driver-bin_1.10" to the LICENSE_FLAGS_WHITELIST variable
77in your local.conf. For example:
78
79 LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.10"
80
75If you want to enable the layer that does not support EMGD graphics 81If you want to enable the layer that does not support EMGD graphics
76add the following to the local.conf file: 82add the following to the local.conf file:
77 83
@@ -97,87 +103,8 @@ equivalently check out the appropriate branch from the meta-intel
97repository at the same location. 103repository at the same location.
98 104
99 105
100II. Special notes for building the meta-crownbay BSP layer 106II. Booting the images in /binary
101========================================================== 107=================================
102
103The meta-crownbay layer makes use of the proprietary Intel EMGD
104userspace drivers when building the "crownbay" machine (but not when
105building the "crownbay-noemgd" machine). If you got the BSP from the
106'BSP Downloads' section of the Yocto website, the EMGD binaries needed
107to perform the build will already be present in the BSP, located in
108the meta-intel/common/recipes-graphics/xorg-xserver/emgd-driver-bin-1.8
109directory, and you can ignore the rest of this section.
110
111If you didn't get the BSP from the 'BSP Downloads' section of the
112Yocto website, you can download a tarball containing an rpm that
113contains the binaries and extract the binaries from that, and copy
114them to the proper location in the meta-crownbay layer.
115
116The following subsection describes that process in detail.
117
118
119Downloading and extracting the binaries using the EMGD Linux tarball
120--------------------------------------------------------------------
121
122The first step of the process is to download the EMGD 1.8 Driver.
123Here is the current link to the URL from which it can be downloaded:
124
125http://edc.intel.com/Software/Downloads/EMGD/
126
127In the Download Now tab, select:
128
129IntelĀ® architecture-based product: Linux Tar Ball
130Operating System: MeeGo* 1.2 IVI Linux* (kernel 2.6.37, X.server 1.9, Mesa 7.9)
131
132That will give you a large .tgz file:
133
134Lin_EMGD_1_8_RC_2032.tgz
135
136Extract the files in the tar file, which will in turn give you a
137directory named IEMGD_HEAD_Linux.
138
139The binaries are contained in an rpm file; you can extract the
140binaries from the rpm file using rpm2cpio and cpio:
141
142$ cd IEMGD_HEAD_Linux/MeeGo1.2
143$ rpm2cpio emgd-bin-2032-1.6.i586.rpm > emgd-bin-2032-1.6.i586.cpio
144$ mkdir extracted; cd extracted
145$ cpio -idv < ../emgd-bin-2032-1.6.i586.cpio
146
147You can now copy the xorg-xserver binaries to the emgd-driver-bin-1.8
148directory in meta-intel/common:
149
150$ cp -a usr/lib meta-intel/common/recipes-graphics/xorg-xserver/emgd-driver-bin-1.8
151
152You also need to copy the IEMGD License.txt file to the same directory:
153
154$ cp IEMGD_HEAD_Linux/License/License.txt meta-intel/common/recipes/xorg-xserver/emgd-driver-bin-1.8
155
156Finally, you need to extract and copy the video plugins to the
157emgd-driver-bin-1.8 directory in meta-intel/common:
158
159$ cd IEMGD_HEAD_Linux/common/video_plugin
160$ rpm2cpio gst-plugins-mixvideo-0.10.30-1.i586.rpm > gst-plugins-mixvideo-0.10.30-1.i586.cpio
161$ rpm2cpio gst-plugins-va-0.10.7MFLD-1.i586.rpm > gst-plugins-va-0.10.7MFLD-1.i586.cpio
162$ rpm2cpio gst-vabuffer-0.10.5MFLD-1.i586.rpm > gst-vabuffer-0.10.5MFLD-1.i586.cpio
163$ rpm2cpio mixcommon-0.1.9-1.i586.rpm > mixcommon-0.1.9-1.i586.cpio
164$ rpm2cpio mixvbp-0.1.24-1.i586.rpm > mixvbp-0.1.24-1.i586.cpio
165$ rpm2cpio mixvideo-0.1.31-1.i586.rpm > mixvideo-0.1.31-1.i586.cpio
166$ mkdir extracted; cd extracted
167$ cpio -idv < ../gst-plugins-mixvideo-0.10.30-1.i586.cpio
168$ cpio -idv < ../gst-plugins-va-0.10.7MFLD-1.i586.cpio
169$ cpio -idv < ../gst-vabuffer-0.10.5MFLD-1.i586.cpio
170$ cpio -idv < ../mixcommon-0.1.9-1.i586.cpio
171$ cpio -idv < ../mixvbp-0.1.24-1.i586.cpio
172$ cpio -idv < ../mixvideo-0.1.31-1.i586.cpio
173$ rm usr/lib/*.so.0
174$ cp -a usr/lib meta-intel/common/recipes-graphics/xorg-xserver/emgd-driver-bin-1.8
175
176At this point, you should be able to build meta-crownbay images as usual.
177
178
179III. Booting the images in /binary
180==================================
181 108
182This BSP contains bootable live images, which can be used to directly 109This BSP contains bootable live images, which can be used to directly
183boot Yocto off of a USB flash drive. 110boot Yocto off of a USB flash drive.