diff options
-rw-r--r-- | meta-crownbay/README | 97 |
1 files changed, 12 insertions, 85 deletions
diff --git a/meta-crownbay/README b/meta-crownbay/README index 65289f71..b56c79a2 100644 --- a/meta-crownbay/README +++ b/meta-crownbay/README | |||
@@ -6,7 +6,7 @@ The Crown Bay platform consists of the Intel Atom Z6xx processor, | |||
6 | plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff). | 6 | plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff). |
7 | 7 | ||
8 | It also supports the E6xx embedded on-chip graphics via the Intel | 8 | It also supports the E6xx embedded on-chip graphics via the Intel |
9 | Embedded Media and Graphics Driver (EMGD) 1.8 Driver. | 9 | Embedded Media and Graphics Driver (EMGD) 1.10 Driver. |
10 | 10 | ||
11 | 11 | ||
12 | Dependencies | 12 | Dependencies |
@@ -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 |
45 | III. Booting the images in /binary | ||
46 | 45 | ||
47 | 46 | ||
48 | I. Building the meta-crownbay BSP layer | 47 | I. Building the meta-crownbay BSP layer |
@@ -64,7 +63,7 @@ common metadata shared between BSPs) e.g.: | |||
64 | The meta-crownbay layer contains support for two different machine | 63 | The meta-crownbay layer contains support for two different machine |
65 | configurations. These configurations are identical except for the fact | 64 | configurations. These configurations are identical except for the fact |
66 | that the one prefixed with 'crownbay' makes use of the | 65 | that the one prefixed with 'crownbay' makes use of the |
67 | Intel-proprietary EMGD 1.8 graphics driver, while the one prefixed | 66 | Intel-proprietary EMGD 1.10 graphics driver, while the one prefixed |
68 | with 'crownbay-noemgd' does not. | 67 | with 'crownbay-noemgd' does not. |
69 | 68 | ||
70 | If you want to enable the layer that supports EMGD graphics add the | 69 | If 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 | ||
74 | The 'crownbay' machine includes the emgd-driver-bin package, which has | ||
75 | a proprietary license that must be whitelisted by adding the string | ||
76 | "license_emgd-driver-bin_1.10" to the LICENSE_FLAGS_WHITELIST variable | ||
77 | in your local.conf. For example: | ||
78 | |||
79 | LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.10" | ||
80 | |||
75 | If you want to enable the layer that does not support EMGD graphics | 81 | If you want to enable the layer that does not support EMGD graphics |
76 | add the following to the local.conf file: | 82 | add the following to the local.conf file: |
77 | 83 | ||
@@ -97,87 +103,8 @@ equivalently check out the appropriate branch from the meta-intel | |||
97 | repository at the same location. | 103 | repository at the same location. |
98 | 104 | ||
99 | 105 | ||
100 | II. Special notes for building the meta-crownbay BSP layer | 106 | II. Booting the images in /binary |
101 | ========================================================== | 107 | ================================= |
102 | |||
103 | The meta-crownbay layer makes use of the proprietary Intel EMGD | ||
104 | userspace drivers when building the "crownbay" machine (but not when | ||
105 | building the "crownbay-noemgd" machine). If you got the BSP from the | ||
106 | 'BSP Downloads' section of the Yocto website, the EMGD binaries needed | ||
107 | to perform the build will already be present in the BSP, located in | ||
108 | the meta-intel/common/recipes-graphics/xorg-xserver/emgd-driver-bin-1.8 | ||
109 | directory, and you can ignore the rest of this section. | ||
110 | |||
111 | If you didn't get the BSP from the 'BSP Downloads' section of the | ||
112 | Yocto website, you can download a tarball containing an rpm that | ||
113 | contains the binaries and extract the binaries from that, and copy | ||
114 | them to the proper location in the meta-crownbay layer. | ||
115 | |||
116 | The following subsection describes that process in detail. | ||
117 | |||
118 | |||
119 | Downloading and extracting the binaries using the EMGD Linux tarball | ||
120 | -------------------------------------------------------------------- | ||
121 | |||
122 | The first step of the process is to download the EMGD 1.8 Driver. | ||
123 | Here is the current link to the URL from which it can be downloaded: | ||
124 | |||
125 | http://edc.intel.com/Software/Downloads/EMGD/ | ||
126 | |||
127 | In the Download Now tab, select: | ||
128 | |||
129 | IntelĀ® architecture-based product: Linux Tar Ball | ||
130 | Operating System: MeeGo* 1.2 IVI Linux* (kernel 2.6.37, X.server 1.9, Mesa 7.9) | ||
131 | |||
132 | That will give you a large .tgz file: | ||
133 | |||
134 | Lin_EMGD_1_8_RC_2032.tgz | ||
135 | |||
136 | Extract the files in the tar file, which will in turn give you a | ||
137 | directory named IEMGD_HEAD_Linux. | ||
138 | |||
139 | The binaries are contained in an rpm file; you can extract the | ||
140 | binaries 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 | |||
147 | You can now copy the xorg-xserver binaries to the emgd-driver-bin-1.8 | ||
148 | directory in meta-intel/common: | ||
149 | |||
150 | $ cp -a usr/lib meta-intel/common/recipes-graphics/xorg-xserver/emgd-driver-bin-1.8 | ||
151 | |||
152 | You 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 | |||
156 | Finally, you need to extract and copy the video plugins to the | ||
157 | emgd-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 | |||
176 | At this point, you should be able to build meta-crownbay images as usual. | ||
177 | |||
178 | |||
179 | III. Booting the images in /binary | ||
180 | ================================== | ||
181 | 108 | ||
182 | This BSP contains bootable live images, which can be used to directly | 109 | This BSP contains bootable live images, which can be used to directly |
183 | boot Yocto off of a USB flash drive. | 110 | boot Yocto off of a USB flash drive. |