diff options
author | Kishore Bodke <kishore.k.bodke@intel.com> | 2013-02-08 14:18:58 -0800 |
---|---|---|
committer | Tom Zanussi <tom.zanussi@linux.intel.com> | 2013-02-16 10:01:30 -0600 |
commit | 1d6b218a45e43441ca6299b899c4d84ec976082c (patch) | |
tree | 1152df28cfdc2e0327ccf361afd241f0d111d004 /meta-cedartrail/README | |
parent | bfa92b97a9d8e4e19d770a87b42a59c16460c1b4 (diff) | |
download | meta-intel-1d6b218a45e43441ca6299b899c4d84ec976082c.tar.gz |
cedartrail: remove BSP
Cedartrail will not be supported in the Yocto 1.4 Release.
Remove it from meta-intel.
Signed-off-by: Kishore Bodke <kishore.k.bodke@intel.com>
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Diffstat (limited to 'meta-cedartrail/README')
-rwxr-xr-x | meta-cedartrail/README | 199 |
1 files changed, 0 insertions, 199 deletions
diff --git a/meta-cedartrail/README b/meta-cedartrail/README deleted file mode 100755 index fe84c2de..00000000 --- a/meta-cedartrail/README +++ /dev/null | |||
@@ -1,199 +0,0 @@ | |||
1 | This README file contains information on building the meta-cedartrail | ||
2 | BSP layer, and booting the images contained in the /binary directory. | ||
3 | Please see the corresponding sections below for details. | ||
4 | |||
5 | The 'Cedar Trail' platform consists of the Intel® Atom™ | ||
6 | N2600/N2800/D2550 processor, plus the Intel® NM10 Express Chispset | ||
7 | (Cedarview + Tiger Point). | ||
8 | |||
9 | It also supports on-chip SGX545 graphics and media accelerator | ||
10 | via the Cedar Trail Power VR (PVR) graphics driver. | ||
11 | |||
12 | Further information about the platforms supported by this BSP can be | ||
13 | found here: | ||
14 | |||
15 | http://www.intel.com/p/en_US/embedded/hwsw/hardware/atom-n2000-d2000/overview | ||
16 | |||
17 | Information on all Intel® embedded platforms can be found here: | ||
18 | |||
19 | http://www.intel.com/p/en_US/embedded/hwsw/hardware | ||
20 | |||
21 | |||
22 | Compliance | ||
23 | ========== | ||
24 | |||
25 | This BSP is compliant with the Yocto Project as per the requirements | ||
26 | listed here: | ||
27 | |||
28 | https://www.yoctoproject.org/webform/yocto-project-compatible-registration | ||
29 | |||
30 | |||
31 | Dependencies | ||
32 | ============ | ||
33 | |||
34 | This layer depends on: | ||
35 | |||
36 | URI: git://git.openembedded.org/bitbake | ||
37 | branch: master | ||
38 | |||
39 | URI: git://git.openembedded.org/openembedded-core | ||
40 | layers: meta | ||
41 | branch: master | ||
42 | |||
43 | URI: git://git.yoctoproject.org/meta-intel | ||
44 | layers: intel | ||
45 | branch: master | ||
46 | |||
47 | |||
48 | Patches | ||
49 | ======= | ||
50 | |||
51 | Please submit any patches against this BSP to the Yocto mailing list | ||
52 | (yocto@yoctoproject.org) and cc: the maintainer: | ||
53 | |||
54 | Maintainer: Kishore Bodke <kishore.k.bodke@intel.com> | ||
55 | |||
56 | Please see the meta-intel/MAINTAINERS file for more details. | ||
57 | |||
58 | Table of Contents | ||
59 | ================= | ||
60 | |||
61 | I. Building the meta-cedartrail BSP layer | ||
62 | II. Booting the images in /binary | ||
63 | |||
64 | |||
65 | I. Building the meta-cedartrail BSP layer | ||
66 | ========================================= | ||
67 | |||
68 | In order to build an image with BSP support for a given release, you | ||
69 | need to download the corresponding BSP tarball from the 'Board Support | ||
70 | Package (BSP) Downloads' page of the Yocto Project website. | ||
71 | |||
72 | Having done that, and assuming you extracted the BSP tarball contents | ||
73 | at the top-level of your yocto build tree, you can build a cedartrail | ||
74 | image by adding the location of the meta-cedartrail layer to | ||
75 | bblayers.conf, along with the meta-intel layer itself (to access | ||
76 | common metadata shared between BSPs) e.g.: | ||
77 | |||
78 | yocto/meta-intel \ | ||
79 | yocto/meta-intel/meta-cedartrail \ | ||
80 | |||
81 | To enable the cedartrail layer that supports Power VR graphics, | ||
82 | add the cedartrail MACHINE to local.conf: | ||
83 | |||
84 | MACHINE ?= "cedartrail" | ||
85 | |||
86 | Power VR Graphics user-space driver binaries are covered by a | ||
87 | "Intel Free Distribution Binary License". The build of this driver | ||
88 | can be enabled by adding the following line to the local.conf file: | ||
89 | |||
90 | LICENSE_FLAGS_WHITELIST += "license_cdv-pvr-driver_1.0.3" | ||
91 | |||
92 | To enable the layer that does not support Power VR graphics | ||
93 | add the following to the local.conf file: | ||
94 | |||
95 | MACHINE ?= "cedartrail-nopvr" | ||
96 | |||
97 | |||
98 | You should then be able to build a cedartrail image as such: | ||
99 | |||
100 | $ source oe-init-build-env | ||
101 | $ bitbake core-image-sato | ||
102 | |||
103 | The above image will not give you the webkit feature and will not | ||
104 | have the Audio and Video media samples in the image. | ||
105 | |||
106 | If you want the webkit feature and Audio , Video media samples built | ||
107 | into the image by default, You should build the custom image by | ||
108 | doing the following: | ||
109 | |||
110 | $ source oe-init-build-env | ||
111 | $ bitbake core-image-cdv-media | ||
112 | |||
113 | At the end of a successful build, you should have a live image that | ||
114 | you can boot from a USB flash drive (see instructions on how to do | ||
115 | that below, in the section 'Booting the images from /binary'). | ||
116 | |||
117 | NOTE: The 'cedartrail' machine will include support for hardware video | ||
118 | acceleration via gstreamer if and only if the "commercial" string is | ||
119 | added to the the LICENSE_FLAGS_WHITELIST variable in your local.conf. | ||
120 | |||
121 | For example: | ||
122 | |||
123 | LICENSE_FLAGS_WHITELIST = "license_cdv-pvr-driver_1.0.3 commercial" | ||
124 | |||
125 | The reason this is needed is to prevent the image from including | ||
126 | anything that might violate the license terms of the packages used to | ||
127 | implement the the video acceleration feature, such as gst-ffmpeg and | ||
128 | ffmpeg. As always, please consult the licenses included in the | ||
129 | specific packages for details if you use packages that require | ||
130 | particular LICENSE_FLAGS. | ||
131 | |||
132 | As an alternative to downloading the BSP tarball, you can also work | ||
133 | directly from the meta-intel git repository. For each BSP in the | ||
134 | 'meta-intel' repository, there are multiple branches, one | ||
135 | corresponding to each major release starting with 'laverne' (0.90), in | ||
136 | addition to the latest code which tracks the current master. Instead | ||
137 | of extracting a BSP tarball at the top level of your yocto build tree, | ||
138 | you can equivalently check out the appropriate branch from the | ||
139 | meta-intel repository at the same location. | ||
140 | |||
141 | |||
142 | II. Booting the images in /binary | ||
143 | ================================== | ||
144 | |||
145 | This BSP contains bootable live images, which can be used to directly | ||
146 | boot Yocto off of a USB flash drive. | ||
147 | |||
148 | Under Linux, insert a USB flash drive. Assuming the USB flash drive | ||
149 | takes device /dev/sdf, use dd to copy the live image to it. For | ||
150 | example: | ||
151 | |||
152 | # dd if=core-image-sato-cedartrail-20120105232035.hddimg of=/dev/sdf | ||
153 | # sync | ||
154 | # eject /dev/sdf | ||
155 | |||
156 | This should give you a bootable USB flash device. Insert the device | ||
157 | into a bootable USB socket on the target, and power on. This should | ||
158 | result in a system booted to the Sato graphical desktop. | ||
159 | |||
160 | If you want a terminal, use the arrows at the top of the UI to move to | ||
161 | different pages of available applications, one of which is named | ||
162 | 'Terminal'. Clicking that should give you a root terminal. | ||
163 | |||
164 | If you want to ssh into the system, you can use the root terminal to | ||
165 | ifconfig the IP address and use that to ssh in. The root password is | ||
166 | empty, so to log in type 'root' for the user name and hit 'Enter' at | ||
167 | the Password prompt: and you should be in. | ||
168 | |||
169 | ---- | ||
170 | |||
171 | If you find you're getting corrupt images on the USB (it doesn't show | ||
172 | the syslinux boot: prompt, or the boot: prompt contains strange | ||
173 | characters), try doing this first: | ||
174 | |||
175 | # dd if=/dev/zero of=/dev/sdf bs=1M count=512 | ||
176 | |||
177 | Miscellaneous Notes | ||
178 | ==================== | ||
179 | |||
180 | Video and Music Samples | ||
181 | ----------------------- | ||
182 | This BSP includes recipes to download Ogg format video and | ||
183 | music files that can be played-back with the Video and music players | ||
184 | included in the sato images. The sample files are installed in | ||
185 | /home/Music and /home/Videos directories. | ||
186 | |||
187 | |||
188 | Adding Glxgears to image | ||
189 | ------------------------- | ||
190 | Glxgears can be added to the generated image by adding "tools-testapps" | ||
191 | option to the extra image features variable in the default local.conf | ||
192 | before building the BSP. | ||
193 | |||
194 | e.g. to add Glxgears, locate the following line in local.conf | ||
195 | EXTRA_IMAGE_FEATURES = "debug-tweaks" | ||
196 | |||
197 | and change above line to.. | ||
198 | |||
199 | EXTRA_IMAGE_FEATURES = "debug-tweaks tools-testapps" | ||