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