diff options
| -rw-r--r-- | meta-crownbay/README | 181 |
1 files changed, 31 insertions, 150 deletions
diff --git a/meta-crownbay/README b/meta-crownbay/README index 89056ed9..439b8c70 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.6 Gold Driver. | 9 | Embedded Media and Graphics Driver (EMGD) 1.8 Driver. |
| 10 | 10 | ||
| 11 | Table of Contents | 11 | Table of Contents |
| 12 | ================= | 12 | ================= |
| @@ -33,10 +33,10 @@ bblayers.conf e.g.: | |||
| 33 | The meta-crownbay layer contains support for two different machine | 33 | The meta-crownbay layer contains support for two different machine |
| 34 | configurations. These configurations are identical except for the fact | 34 | configurations. These configurations are identical except for the fact |
| 35 | that the one prefixed with 'crownbay' makes use of the | 35 | that the one prefixed with 'crownbay' makes use of the |
| 36 | Intel-proprietary EMGD 1.6 graphics driver, while the one prefixed | 36 | Intel-proprietary EMGD 1.8 graphics driver, while the one prefixed |
| 37 | with 'crownbay-noemgd' does not. | 37 | with 'crownbay-noemgd' does not. |
| 38 | 38 | ||
| 39 | If you want to enable the layer that supports EMGD graphics add | 39 | If you want to enable the layer that supports EMGD graphics add the |
| 40 | following to the local.conf file: | 40 | following 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 | ||
| 49 | You should then be able to build a crownbay image as such: | 49 | You 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 | ||
| 54 | At the end of a successful build, you should have a live image that | 54 | At the end of a successful build, you should have a live image that |
| 55 | you can boot from a USB flash drive (see instructions on how to do | 55 | you 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 | |||
| 59 | directly from the meta-intel git repository. For each BSP in the | 59 | directly 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 |
| 61 | corresponding to each major release starting with 'laverne' (0.90), in | 61 | corresponding to each major release starting with 'laverne' (0.90), in |
| 62 | addition to the latest code which tracks the current master. Instead | 62 | addition to the latest code which tracks the current master (note that |
| 63 | of extracting a BSP tarball at the top level of your yocto build tree, | 63 | not all BSPs are present in every release). Instead of extracting |
| 64 | you can equivalently check out the appropriate branch from the | 64 | a BSP tarball at the top level of your yocto build tree, you can |
| 65 | meta-intel repository at the same location. | 65 | equivalently check out the appropriate branch from the meta-intel |
| 66 | repository at the same location. | ||
| 66 | 67 | ||
| 67 | 68 | ||
| 68 | II. Special notes for building the meta-crownbay BSP layer | 69 | II. Special notes for building the meta-crownbay BSP layer |
| @@ -73,39 +74,33 @@ userspace drivers when building the "crownbay" machine (but not when | |||
| 73 | building the "crownbay-noemgd" machine). If you got the BSP from the | 74 | building 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 |
| 75 | to perform the build will already be present in the BSP, located in | 76 | to perform the build will already be present in the BSP, located in |
| 76 | the recipes-graphics/xorg-xserver/emgd-driver-bin-1.6 directory, and | 77 | the meta-intel/common/recipes-graphics/xorg-xserver/emgd-driver-bin-1.8 |
| 77 | you can ignore the rest of this section. | 78 | directory, and you can ignore the rest of this section. |
| 78 | 79 | ||
| 79 | If you didn't get the BSP from the 'BSP Downloads' section of the | 80 | If you didn't get the BSP from the 'BSP Downloads' section of the |
| 80 | Yocto website, you have two choices: | 81 | Yocto website, you can download a tarball containing an rpm that |
| 82 | contains the binaries and extract the binaries from that, and copy | ||
| 83 | them to the proper location in the meta-crownbay layer. | ||
| 81 | 84 | ||
| 82 | - You can download a tarball containing an rpm that contains the | 85 | The 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 | ||
| 90 | The following subsections describe each option in detail. | 88 | Downloading and extracting the binaries using the EMGD Linux tarball |
| 89 | -------------------------------------------------------------------- | ||
| 91 | 90 | ||
| 92 | 91 | The first step of the process is to download the EMGD 1.8 Driver. | |
| 93 | IIa Downloading and extracting the binaries using the EMGD Linux tarball | 92 | Here is the current link to the URL from which it can be downloaded: |
| 94 | ------------------------------------------------------------------------ | ||
| 95 | |||
| 96 | The first step of the process is to download the EMGD 1.6 Gold Driver. | ||
| 97 | Here is the current link to the URL which it can be downloaded from: | ||
| 98 | 93 | ||
| 99 | http://edc.intel.com/Software/Downloads/EMGD/ | 94 | http://edc.intel.com/Software/Downloads/EMGD/ |
| 100 | 95 | ||
| 101 | In the Download Now tab, select: | 96 | In the Download Now tab, select: |
| 102 | 97 | ||
| 103 | Intel® architecture-based product: Linux Tar Ball | 98 | Intel® architecture-based product: Linux Tar Ball |
| 104 | Operating System: MeeGo 1.0 IVI Linux (kernel 2.6.33.3, X.server 1.8.0) | 99 | Operating System: MeeGo* 1.2 IVI Linux* (kernel 2.6.37, X.server 1.9, Mesa 7.9) |
| 105 | 100 | ||
| 106 | That will give you a large tar file: | 101 | That will give you a large .tgz file: |
| 107 | 102 | ||
| 108 | Lin_EMGD_1_6_RC_1922.tar | 103 | Lin_EMGD_1_8_RC_2032.tgz |
| 109 | 104 | ||
| 110 | Extract the files in the tar file, which will in turn give you a | 105 | Extract the files in the tar file, which will in turn give you a |
| 111 | directory named IEMGD_HEAD_Linux. | 106 | directory named IEMGD_HEAD_Linux. |
| @@ -114,138 +109,24 @@ The binaries are contained in an rpm file; you can extract the | |||
| 114 | binaries from the rpm file using rpm2cpio and cpio: | 109 | binaries 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 | ||
| 121 | Finally, you can copy the xorg-xserver binaries to the | 116 | Finally, you can copy the xorg-xserver binaries to the |
| 122 | emgd-driver-bin-1.6 directory in the meta-crownbay layer: | 117 | emgd-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 | ||
| 126 | You also need to copy the IEMGD License.txt file to the same directory: | 121 | You 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 | ||
| 130 | At this point, you should be able to build meta-crownbay images as usual. | 125 | At this point, you should be able to build meta-crownbay images as usual. |
| 131 | 126 | ||
| 132 | 127 | ||
| 133 | IIb Extracting the binaries using the graphical ced application | 128 | III. Booting the images in /binary |
| 134 | --------------------------------------------------------------- | 129 | ================================== |
| 135 | |||
| 136 | These steps require that you run a graphical application in Windows. | ||
| 137 | Windows 7 was used for these instructions, but it shouldn't matter | ||
| 138 | which version of Windows you use. | ||
| 139 | |||
| 140 | The first step of the process is to download the EMGD 1.6 Gold Driver. | ||
| 141 | Here is the current link to the URL which it can be downloaded from: | ||
| 142 | |||
| 143 | http://edc.intel.com/Software/Downloads/EMGD/ | ||
| 144 | |||
| 145 | In the Download Now tab, select: | ||
| 146 | |||
| 147 | Intel® architecture-based product: Intel Atom Processor E6XX Series | ||
| 148 | Operating System: MeeGo 1.0 IVI Linux (kernel 2.6.33.3, X.server 1.8.0) | ||
| 149 | |||
| 150 | That will give you a large zip file: | ||
| 151 | |||
| 152 | IEMGD_1_6_GOLD_1922.zip | ||
| 153 | |||
| 154 | Extract the files in the zip file, which will in turn give you a large | ||
| 155 | .exe file: | ||
| 156 | |||
| 157 | IEMGD_1_6_GOLD_ALL_1922.exe | ||
| 158 | |||
| 159 | Run IEMGD_1_6_GOLD_ALL_1922.exe to install, accept licenses, etc. | ||
| 160 | |||
| 161 | If it says to install watcom, follow the instructions to do that. | ||
| 162 | |||
| 163 | When the installation completes, an application named "emgd-ced" will | ||
| 164 | be present in the install directory. Double-click to run it. | ||
| 165 | |||
| 166 | Select the menu item: New Configuration | ||
| 167 | |||
| 168 | In the tabbed page, make the following selections and/or enter the | ||
| 169 | specified data: | ||
| 170 | |||
| 171 | Configuration File Name: myconfig | ||
| 172 | Platform Chipset: Intel Atom Processor E6xx | ||
| 173 | Port Devices: LVDS, sDVO | ||
| 174 | |||
| 175 | Hit the 'Next' button. | ||
| 176 | |||
| 177 | On the next tabbed page, make the following selections and/or enter | ||
| 178 | the specified data: | ||
| 179 | |||
| 180 | Readable Port Name: portname0 | ||
| 181 | Encoder Configuration: Select sDVO Device: Internal LVDS | ||
| 182 | |||
| 183 | Hit the 'Finish' button. | ||
| 184 | |||
| 185 | Select the menu item: New Package | ||
| 186 | |||
| 187 | In the tabbed page, make the following selections and/or enter the | ||
| 188 | specified data: | ||
| 189 | |||
| 190 | Package File Name: mypackage | ||
| 191 | Configurations: selec myconfig.cnfg | ||
| 192 | Target OS: Linux operating System | ||
| 193 | |||
| 194 | Hit the 'Finish' button. | ||
| 195 | |||
| 196 | Select the menu item: Generate Installation | ||
| 197 | |||
| 198 | This will create the EMGD installation package: | ||
| 199 | |||
| 200 | Generating EMGD installation... | ||
| 201 | |||
| 202 | The installation package should now be under the 'workspace' | ||
| 203 | subdirectory of the directory you installed to: | ||
| 204 | |||
| 205 | workspace/installation/mypackage.pkg_installation/IEMGD_HEAD_Linux/IEMGD_HEAD_Linux.tgz | ||
| 206 | |||
| 207 | This is the file you are interested in. Copy it to your Poky build | ||
| 208 | system, and uncompress/untar it: | ||
| 209 | |||
| 210 | $ tar cvfz IEMGD_HEAD_Linux.tgz | ||
| 211 | |||
| 212 | The binaries are contained in an rpm file; you can extract the | ||
| 213 | binaries 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 | |||
| 220 | Finally, you can copy the xorg-xserver binaries to the | ||
| 221 | emgd-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 | |||
| 225 | You 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 | |||
| 229 | At this point, you should be able to build meta-crownbay images as usual. | ||
| 230 | |||
| 231 | ---- | ||
| 232 | |||
| 233 | For reference, the EMGD Driver documentation is also available at the | ||
| 234 | above link. | ||
| 235 | |||
| 236 | The specific text of the document is: | ||
| 237 | |||
| 238 | User Guide: Intel® Embedded Media and Graphics Driver, EFI Video | ||
| 239 | Driver, EPOG, and Video BIOS v1.6 for Windows* XP and Linux* Provides | ||
| 240 | installation requirements/procedures & describes the vbios/firmware, | ||
| 241 | configuration options, & functionality of Intel® EMGD under Windows* & | ||
| 242 | Linux*. Refer to guide for details. | ||
| 243 | |||
| 244 | April 2011 | ||
| 245 | |||
| 246 | |||
| 247 | II. Booting the images in /binary | ||
| 248 | ================================= | ||
| 249 | 130 | ||
| 250 | This BSP contains bootable live images, which can be used to directly | 131 | This BSP contains bootable live images, which can be used to directly |
| 251 | boot Yocto off of a USB flash drive. | 132 | boot Yocto off of a USB flash drive. |
| @@ -254,7 +135,7 @@ Under Linux, insert a USB flash drive. Assuming the USB flash drive | |||
| 254 | takes device /dev/sdf, use dd to copy the live image to it. For | 135 | takes device /dev/sdf, use dd to copy the live image to it. For |
| 255 | example: | 136 | example: |
| 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 | ||
