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