summaryrefslogtreecommitdiffstats
path: root/meta-crownbay/README
diff options
context:
space:
mode:
authorTom Zanussi <tom.zanussi@intel.com>2010-12-13 22:40:15 -0600
committerSaul Wold <sgw@linux.intel.com>2011-01-03 16:45:27 -0800
commit7059fe6442b0cf480261fbcdea3e5ba404afef27 (patch)
tree229efc2453e72560d5d89551753d388f36fb2c61 /meta-crownbay/README
parentc14f24a2e9aebaaf2edb005f9480b395a8618acf (diff)
downloadmeta-intel-7059fe6442b0cf480261fbcdea3e5ba404afef27.tar.gz
meta-crownbay: new layer for E6xx/EG20T systems
This layer provides support for Tunnel Creek + Topcliff Intel systems to laverne (0.90). It supports the E6xx embedded on-chip graphics via the Intel Embedded Media and Graphics Driver (EMGD) 1.5 Gold Driver. The EMGD and EG20T PCH kernel drivers are of course GPL'ed and are submitted in a separate patchset for the 2.6.34 yocto kernel. The userspace X drivers and supporting libraries however are closed and need to be manually copied into the layer before building. The details on how to do this can be found in the README doc in meta-crownbay/. Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Diffstat (limited to 'meta-crownbay/README')
-rw-r--r--meta-crownbay/README198
1 files changed, 198 insertions, 0 deletions
diff --git a/meta-crownbay/README b/meta-crownbay/README
new file mode 100644
index 00000000..f0a710b8
--- /dev/null
+++ b/meta-crownbay/README
@@ -0,0 +1,198 @@
1This README file contains information on building the meta-crownbay
2BSP layer, and booting the images contained in the /binary directory.
3Please see the corresponding sections below for details.
4
5
6Table of Contents
7=================
8
9 I. Building the meta-crownbay BSP layer
10 II. Special notes for building the meta-crownbay BSP layer
11III. Booting the images in /binary
12
13
14I. Building the meta-crownbay BSP layer
15=======================================
16
17For each BSP in the 'meta-intel' repository, there are multiple
18branches, one corresponding to each major release starting with
19'laverne' (0.90), in addition to the latest code which tracks the
20current master.
21
22In order to build an image with BSP support for a given release, you
23need to check out the 'meta-intel' branch corresponding to the release
24you're building against e.g. to build for laverne (0.90), check out
25the 'laverne' branch of both poky and 'meta-intel'.
26
27Having done that, and assuming you cloned the 'meta-intel' repository
28at the top-level of your yocto build tree, you can build a crownbay
29image by adding the location of the meta-crownbay layer to
30bblayers.conf e.g.:
31
32 yocto/meta-intel/meta-crownbay \
33
34To enable the crownbay layer, add the crownbay MACHINE to local.conf:
35
36 MACHINE ?= "crownbay"
37
38You should then be able to build a crownbay image as such:
39
40 $ source poky-init-build-env
41 $ bitbake poky-image-sato-live
42
43At the end of a successful build, you should have a live image that
44you can boot from a USB flash drive (see instructions on how to do
45that below, in the section 'Booting the images from /binary').
46
47
48II. Special notes for building the meta-crownbay BSP layer
49==========================================================
50
51The meta-crownbay layer makes use of the proprietary Intel EMGD
52userspace drivers, which at this point in time require that the user
53accept the Intel license by manually extracting the binaries and
54copying them to the proper location in the meta-crownbay layer.
55
56There currently isn't an automated way to do this, thus the manual
57step. When Yocto supports a click-through installation mechanism, the
58binary files will be packaged as part of the recipe, and this step
59will be unnecessary.
60
61These steps require that you run a graphical application in Windows.
62Windows 7 was used for these instructions, but it shouldn't matter
63which version of Windows you use.
64
65The first step of the process is to download the EMGD 1.5 Gold Driver.
66Here is the current link to the URL which it can be downloaded from:
67
68http://edc.intel.com/Software/Downloads/EMGD/
69
70In the Download Now tab, select:
71
72Intel® architecture-based product: Intel Atom Processor E6XX Series
73Operating System: MeeGo 1.0 IVI Linux (kernel 2.6.33.3, X.server 1.8.0)
74
75That will give you a large zip file:
76
77IEMGD_1_5_GOLD_ALL_1742.zip
78
79Extract the files in the zip file, which will in turn give you a large
80.exe file:
81
82IEMGD_1_5_GOLD_ALL_1742.exe
83
84Run IEMGD_1_5_GOLD_ALL_1742.exe to install, accept licenses, etc.
85
86If it says to install watcom, follow the instructions to do that.
87
88When the installation completes, an application named "emgd-ced" will
89be present in the install directory. Double-click to run it.
90
91Select the menu item: New Configuration
92
93In the tabbed page, make the following selections and/or enter the
94specified data:
95
96Configuration File Name: myconfig
97Platform Chipset: Intel Atom Processor E6xx
98Port Devices: LVDS, sDVO
99
100Hit the 'Next' button.
101
102On the next tabbed page, make the following selections and/or enter
103the specified data:
104
105Readable Port Name: portname0
106Encoder Configuration: Select sDVO Device: Internal LVDS
107
108Hit the 'Finish' button.
109
110Select the menu item: New Package
111
112In the tabbed page, make the following selections and/or enter the
113specified data:
114
115Package File Name: mypackage
116Configurations: selec myconfig.cnfg
117Target OS: Linux operating System
118
119Hit the 'Finish' button.
120
121Select the menu item: Generate Installation
122
123This will create the EMGD installation package:
124
125Generating EMGD installation...
126
127The installation package should now be under the 'workspace'
128subdirectory of the directory you installed to:
129
130workspace/installation/mypackage.pkg_installation/IEMGD_HEAD_Linux/IEMGD_HEAD_Linux.tgz
131
132This is the file you are interested in. Copy it to your Poky build
133system, and uncompress/untar it:
134
135$ tar cvfz IEMGD_HEAD_Linux.tgz
136
137Finally, copy Xorg-xserver binaries in the Meego1.0 driver directory
138to the xserver-xf86-emgd-bin directory in the meta-crownbay layer:
139
140$ cp IEMGD_HEAD_Linux/MeeGo1.0/driver/Xorg-xserver-1.7.99/* meta-crownbay/recipes/xorg-xserver/xserver-xf86-emgd-bin
141
142You also need to copy the IEMGD License.txt file to the same directory:
143
144$ cp IEMGD_HEAD_Linux/License/License.txt meta-crownbay/recipes/xorg-xserver/xserver-xf86-emgd-bin
145
146At this point, you should be able to build meta-crownbay images as usual.
147
148----
149
150For reference, the EMGD Driver documentation is also available at the
151above link (it's also part of the installation).
152
153The specific text of the document is:
154
155User Guide: Intel® Embedded Media and Graphics Driver, EFI Video
156Driver, EPOG, and Video BIOS v1.5 for Windows* XP and Linux* Provides
157installation requirements/procedures & describes the vbios/firmware,
158configuration options, & functionality of Intel® EMGD under Windows* &
159Linux*. Refer to guide for details.
160
161File Type/Size: PDF 3,340KB
162Version: 008 : October 2010
163
164
165II. Booting the images in /binary
166=================================
167
168This BSP contains bootable live images, which can be used to directly
169boot Yocto off of a USB flash drive.
170
171Under Linux, insert a USB flash drive. Assuming the USB flash drive
172takes device /dev/sdf, use dd to copy the live image to it. For
173example:
174
175# dd if=poky-image-sato-live-crownbay-20101207053738.hddimg of=/dev/sdf
176# sync
177# eject /dev/sdf
178
179This should give you a bootable USB flash device. Insert the device
180into a bootable USB socket on the target, and power on. This should
181result in a system booted to the Sato graphical desktop.
182
183If you want a terminal, use the arrows at the top of the UI to move to
184different pages of available applications, one of which is named
185'Terminal'. Clicking that should give you a root terminal.
186
187If you want to ssh into the system, you can use the root terminal to
188ifconfig the IP address and use that to ssh in. The root password is
189empty, so to log in type 'root' for the user name and hit 'Enter' at
190the Password prompt: and you should be in.
191
192----
193
194If you find you're getting corrupt images on the USB (it doesn't show
195the syslinux boot: prompt, or the boot: prompt contains strange
196characters), try doing this first:
197
198# dd if=/dev/zero of=/dev/sdf bs=1M count=512