diff options
Diffstat (limited to 'meta-fri2/README')
-rw-r--r-- | meta-fri2/README | 108 |
1 files changed, 94 insertions, 14 deletions
diff --git a/meta-fri2/README b/meta-fri2/README index 7957a7fe..29f26183 100644 --- a/meta-fri2/README +++ b/meta-fri2/README | |||
@@ -2,36 +2,56 @@ This README file contains information on building the meta-fri2 BSP | |||
2 | layer, and booting the images contained in the /binary directory. | 2 | layer, and booting the images contained in the /binary directory. |
3 | Please see the corresponding sections below for details. | 3 | Please see the corresponding sections below for details. |
4 | 4 | ||
5 | The Fish River Island II platform consists of the Intel Atom Z6xx | ||
6 | processor, plus the Intel EG20T Platform Controller Hub (Tunnel Creek | ||
7 | + Topcliff), along with a varied assortment of communications options | ||
8 | and various other machine-to-machine (m2m) capabilities. | ||
9 | |||
10 | It also supports the E6xx embedded on-chip graphics via the Intel | ||
11 | Embedded Media and Graphics Driver (EMGD) 1.8 Driver. | ||
12 | |||
5 | 13 | ||
6 | Table of Contents | 14 | Table of Contents |
7 | ================= | 15 | ================= |
8 | 16 | ||
9 | I. Special notes on the meta-fri2 BSP layer | 17 | I. Building the meta-fri2 BSP layer |
10 | II. Building the meta-fri2 BSP layer | 18 | II. Special notes for building the meta-fri2 BSP layer |
11 | III. Booting the images in /binary | 19 | III. Booting the images in /binary |
12 | 20 | ||
13 | 21 | ||
14 | II. Building the meta-fri2 BSP layer | 22 | I. Building the meta-fri2 BSP layer |
15 | ========================================= | 23 | =================================== |
16 | 24 | ||
17 | In order to build an image with BSP support for a given release, you | 25 | In order to build an image with BSP support for a given release, you |
18 | need to download the corresponding BSP tarball from the 'Board Support | 26 | need to download the corresponding BSP tarball from the 'Board Support |
19 | Package (BSP) Downloads' page of the Yocto Project website. | 27 | Package (BSP) Downloads' page of the Yocto Project website. |
20 | 28 | ||
21 | Having done that, and assuming you extracted the BSP tarball contents | 29 | Having done that, and assuming you extracted the BSP tarball contents |
22 | at the top-level of your yocto build tree, you can build a fri2 image | 30 | at the top-level of your yocto build tree, you can build an fri2 image |
23 | by adding the location of the meta-fri2 layer to bblayers.conf e.g.: | 31 | by adding the location of the meta-fri2 layer to bblayers.conf e.g.: |
24 | 32 | ||
25 | yocto/meta-intel/meta-fri2 \ | 33 | yocto/meta-intel/meta-fri2 \ |
26 | 34 | ||
27 | To enable the fri2 layer, add the fri2 MACHINE to local.conf: | 35 | The meta-fri2 layer contains support for two different machine |
36 | configurations. These configurations are identical except for the fact | ||
37 | that the one prefixed with 'fri2' makes use of the Intel-proprietary | ||
38 | EMGD 1.8 graphics driver, while the one prefixed with 'fri2-noemgd' | ||
39 | does not. | ||
40 | |||
41 | If you want to enable the layer that supports EMGD graphics add the | ||
42 | following to the local.conf file: | ||
28 | 43 | ||
29 | MACHINE ?= "fri2" | 44 | MACHINE ?= "fri2" |
30 | 45 | ||
31 | You should then be able to build a fri2 image as such: | 46 | If you want to enable the layer that does not support EMGD graphics |
47 | add the following to the local.conf file: | ||
48 | |||
49 | MACHINE ?= "fri2-noemgd" | ||
32 | 50 | ||
33 | $ source poky-init-build-env | 51 | You should then be able to build an fri2 image as such: |
34 | $ bitbake poky-image-sato-live | 52 | |
53 | $ source oe-init-build-env | ||
54 | $ bitbake core-image-sato | ||
35 | 55 | ||
36 | At the end of a successful build, you should have a live image that | 56 | At the end of a successful build, you should have a live image that |
37 | you can boot from a USB flash drive (see instructions on how to do | 57 | you can boot from a USB flash drive (see instructions on how to do |
@@ -41,10 +61,70 @@ As an alternative to downloading the BSP tarball, you can also work | |||
41 | directly from the meta-intel git repository. For each BSP in the | 61 | directly from the meta-intel git repository. For each BSP in the |
42 | 'meta-intel' repository, there are multiple branches, one | 62 | 'meta-intel' repository, there are multiple branches, one |
43 | corresponding to each major release starting with 'laverne' (0.90), in | 63 | corresponding to each major release starting with 'laverne' (0.90), in |
44 | addition to the latest code which tracks the current master. Instead | 64 | addition to the latest code which tracks the current master (note that |
45 | of extracting a BSP tarball at the top level of your yocto build tree, | 65 | not all BSPs are present in every release). Instead of extracting a |
46 | you can equivalently check out the appropriate branch from the | 66 | BSP tarball at the top level of your yocto build tree, you can |
47 | meta-intel repository at the same location. | 67 | equivalently check out the appropriate branch from the meta-intel |
68 | repository at the same location. | ||
69 | |||
70 | |||
71 | II. Special notes for building the meta-fri2 BSP layer | ||
72 | ====================================================== | ||
73 | |||
74 | The meta-fri2 layer makes use of the proprietary Intel EMGD userspace | ||
75 | drivers when building the "fri2" machine (but not when building the | ||
76 | "fri2-noemgd" machine). If you got the BSP from the 'BSP Downloads' | ||
77 | section of the Yocto website, the EMGD binaries needed to perform the | ||
78 | build will already be present in the BSP, located in the | ||
79 | meta-intel/common/recipes-graphics/xorg-xserver/emgd-driver-bin-1.8 | ||
80 | directory, and you can ignore the rest of this section. | ||
81 | |||
82 | If you didn't get the BSP from the 'BSP Downloads' section of the | ||
83 | Yocto website, you can download a tarball containing an rpm that | ||
84 | contains the binaries and extract the binaries from that, and copy | ||
85 | them to the proper location in the meta-fri2 layer. | ||
86 | |||
87 | The following subsection describes that process in detail. | ||
88 | |||
89 | |||
90 | Downloading and extracting the binaries using the EMGD Linux tarball | ||
91 | -------------------------------------------------------------------- | ||
92 | |||
93 | The first step of the process is to download the EMGD 1.8 Driver. | ||
94 | Here is the current link to the URL from which it can be downloaded: | ||
95 | |||
96 | http://edc.intel.com/Software/Downloads/EMGD/ | ||
97 | |||
98 | In the Download Now tab, select: | ||
99 | |||
100 | IntelĀ® architecture-based product: Linux Tar Ball | ||
101 | Operating System: MeeGo* 1.2 IVI Linux* (kernel 2.6.37, X.server 1.9, Mesa 7.9) | ||
102 | |||
103 | That will give you a large .tgz file: | ||
104 | |||
105 | Lin_EMGD_1_8_RC_2032.tgz | ||
106 | |||
107 | Extract the files in the tar file, which will in turn give you a | ||
108 | directory named IEMGD_HEAD_Linux. | ||
109 | |||
110 | The binaries are contained in an rpm file; you can extract the | ||
111 | binaries from the rpm file using rpm2cpio and cpio: | ||
112 | |||
113 | $ cd IEMGD_HEAD_Linux/MeeGo1.2 | ||
114 | $ rpm2cpio emgd-bin-2032-1.6.i586.rpm > emgd-bin-2032-1.6.i586.cpio | ||
115 | $ mkdir extracted; cd extracted | ||
116 | $ cpio -idv < ../emgd-bin-2032-1.6.i586.cpio | ||
117 | |||
118 | Finally, you can copy the xorg-xserver binaries to the | ||
119 | emgd-driver-bin-1.8 directory in meta-intel/common: | ||
120 | |||
121 | $ cp -a usr/lib meta-intel/common/recipes-graphics/xorg-xserver/emgd-driver-bin-1.8 | ||
122 | |||
123 | You also need to copy the IEMGD License.txt file to the same directory: | ||
124 | |||
125 | $ cp IEMGD_HEAD_Linux/License/License.txt meta-intel/common/recipes/xorg-xserver/emgd-driver-bin-1.8 | ||
126 | |||
127 | At this point, you should be able to build meta-fri2 images as usual. | ||
48 | 128 | ||
49 | 129 | ||
50 | III. Booting the images in /binary | 130 | III. Booting the images in /binary |
@@ -57,7 +137,7 @@ Under Linux, insert a USB flash drive. Assuming the USB flash drive | |||
57 | takes device /dev/sdf, use dd to copy the live image to it. For | 137 | takes device /dev/sdf, use dd to copy the live image to it. For |
58 | example: | 138 | example: |
59 | 139 | ||
60 | # dd if=poky-image-sato-live-fri2-20101207053738.hddimg of=/dev/sdf | 140 | # dd if=core-image-sato-fri2-20101207053738.hddimg of=/dev/sdf |
61 | # sync | 141 | # sync |
62 | # eject /dev/sdf | 142 | # eject /dev/sdf |
63 | 143 | ||