diff options
Diffstat (limited to 'meta-sys940x/README')
-rw-r--r-- | meta-sys940x/README | 178 |
1 files changed, 0 insertions, 178 deletions
diff --git a/meta-sys940x/README b/meta-sys940x/README deleted file mode 100644 index 57f64f23..00000000 --- a/meta-sys940x/README +++ /dev/null | |||
@@ -1,178 +0,0 @@ | |||
1 | This README file contains information on building the meta-sys940x BSP | ||
2 | layer, and booting the images contained in the /binary directory. | ||
3 | Please see the corresponding sections below for details. | ||
4 | |||
5 | The 'Queens Bay' platform consists of the Intel Atom E6xx | ||
6 | processor, plus the Intel EG20T Platform Controller Hub (Tunnel Creek | ||
7 | + Topcliff). | ||
8 | |||
9 | It also supports the E6xx embedded on-chip graphics via the Intel | ||
10 | Embedded Media and Graphics Driver (EMGD). | ||
11 | |||
12 | More details available on the product page: | ||
13 | http://www.inforcecomputing.com/SYS940X_ECX.html | ||
14 | |||
15 | Information on all IntelĀ® embedded platforms can be found here: | ||
16 | |||
17 | http://www.intel.com/p/en_US/embedded/hwsw/hardware | ||
18 | |||
19 | |||
20 | Yocto Project Compatible | ||
21 | ======================== | ||
22 | |||
23 | This BSP is compatible with the Yocto Project as per the requirements | ||
24 | listed here: | ||
25 | |||
26 | https://www.yoctoproject.org/webform/yocto-project-compatible-registration | ||
27 | |||
28 | |||
29 | Dependencies | ||
30 | ============ | ||
31 | |||
32 | This layer depends on: | ||
33 | |||
34 | URI: git://git.openembedded.org/bitbake | ||
35 | branch: master | ||
36 | |||
37 | URI: git://git.openembedded.org/openembedded-core | ||
38 | layers: meta | ||
39 | branch: master | ||
40 | |||
41 | URI: git://git.yoctoproject.org/meta-intel | ||
42 | layers: intel | ||
43 | branch: master | ||
44 | |||
45 | |||
46 | Patches | ||
47 | ======= | ||
48 | |||
49 | Please submit any patches against this BSP to the Yocto mailing list | ||
50 | (yocto@yoctoproject.org) and cc: the maintainer: | ||
51 | |||
52 | Maintainer: Darren Hart <dvhart@linux.intel.com> | ||
53 | |||
54 | Please see the meta-intel/MAINTAINERS file for more details. | ||
55 | |||
56 | |||
57 | Table of Contents | ||
58 | ================= | ||
59 | |||
60 | I. Building the meta-sys940x BSP layer | ||
61 | II. Booting the images in /binary | ||
62 | |||
63 | |||
64 | I. Building the meta-sys940x BSP layer | ||
65 | =================================== | ||
66 | |||
67 | In order to build an image with BSP support for a given release, you | ||
68 | need to download the corresponding BSP tarball from the 'Board Support | ||
69 | Package (BSP) Downloads' page of the Yocto Project website. | ||
70 | |||
71 | Having done that, and assuming you extracted the BSP tarball contents | ||
72 | at the top-level of your yocto build tree, you can build an sys940x image | ||
73 | by adding the location of the meta-sys940x layer to bblayers.conf, along | ||
74 | with the meta-intel layer itself (to access common metadata shared | ||
75 | between BSPs) e.g.: | ||
76 | |||
77 | yocto/meta-intel \ | ||
78 | yocto/meta-intel/meta-sys940x \ | ||
79 | |||
80 | The meta-sys940x layer contains support for two different machine | ||
81 | configurations. These configurations are identical except for the fact | ||
82 | that the one prefixed with 'sys940x' makes use of the Intel-proprietary | ||
83 | EMGD graphics driver, while the one prefixed with 'sys940x-noemgd' | ||
84 | does not. | ||
85 | |||
86 | If you want to enable the layer that supports EMGD graphics add the | ||
87 | following to the local.conf file: | ||
88 | |||
89 | MACHINE ?= "sys940x" | ||
90 | |||
91 | The 'sys940x' machine includes the emgd-driver-bin package, which has a | ||
92 | proprietary license that must be whitelisted by adding the string | ||
93 | "license_emgd-driver-bin" to the LICENSE_FLAGS_WHITELIST variable | ||
94 | in your local.conf. For example: | ||
95 | |||
96 | LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin" | ||
97 | |||
98 | The emgd recipe depends on Xorg's dri and glx modules, which are built | ||
99 | only when 'opengl' is listed in DISTRO_FEATURES. So if the distro | ||
100 | doesn't list 'opengl' in the DISTRO_FEATURES you would need this | ||
101 | additional line to your local.conf: | ||
102 | |||
103 | DISTRO_FEATURES_append = " opengl" | ||
104 | |||
105 | If you want to enable the layer that does not support EMGD graphics | ||
106 | add the following to the local.conf file: | ||
107 | |||
108 | MACHINE ?= "sys940x-noemgd" | ||
109 | |||
110 | You should then be able to build an sys940x image as such: | ||
111 | |||
112 | $ source oe-init-build-env | ||
113 | $ bitbake core-image-sato | ||
114 | |||
115 | At the end of a successful build, you should have a live image that | ||
116 | you can boot from a USB flash drive (see instructions on how to do | ||
117 | that below, in the section 'Booting the images from /binary'). | ||
118 | |||
119 | NOTE: The 'sys940x' machine will include support for hardware video | ||
120 | acceleration via gstreamer if and only if the "commercial" string is | ||
121 | added to the the LICENSE_FLAGS_WHITELIST variable in your local.conf. | ||
122 | |||
123 | For example: | ||
124 | |||
125 | LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" | ||
126 | |||
127 | The reason this is needed is to prevent the image from including | ||
128 | anything that might violate the license terms of the packages used to | ||
129 | implement the the video acceleration feature, such as gst-ffmpeg and | ||
130 | ffmpeg. As always, please consult the licenses included in the | ||
131 | specific packages for details if you use packages that require | ||
132 | particular LICENSE_FLAGS. | ||
133 | |||
134 | As an alternative to downloading the BSP tarball, you can also work | ||
135 | directly from the meta-intel git repository. For each BSP in the | ||
136 | 'meta-intel' repository, there are multiple branches, one | ||
137 | corresponding to each major release starting with 'laverne' (0.90), in | ||
138 | addition to the latest code which tracks the current master (note that | ||
139 | not all BSPs are present in every release). Instead of extracting a | ||
140 | BSP tarball at the top level of your yocto build tree, you can | ||
141 | equivalently check out the appropriate branch from the meta-intel | ||
142 | repository at the same location. | ||
143 | |||
144 | |||
145 | II. Booting the images in /binary | ||
146 | ================================= | ||
147 | |||
148 | This BSP contains bootable live images, which can be used to directly | ||
149 | boot Yocto off of a USB flash drive. | ||
150 | |||
151 | Under Linux, insert a USB flash drive. Assuming the USB flash drive | ||
152 | takes device /dev/sdf, use dd to copy the live image to it. For | ||
153 | example: | ||
154 | |||
155 | # dd if=core-image-sato-sys940x.hddimg of=/dev/sdf | ||
156 | # sync | ||
157 | # eject /dev/sdf | ||
158 | |||
159 | This should give you a bootable USB flash device. Insert the device | ||
160 | into a bootable USB socket on the target, and power on. This should | ||
161 | result in a system booted to the Sato graphical desktop. | ||
162 | |||
163 | If you want a terminal, use the arrows at the top of the UI to move to | ||
164 | different pages of available applications, one of which is named | ||
165 | 'Terminal'. Clicking that should give you a root terminal. | ||
166 | |||
167 | If you want to ssh into the system, you can use the root terminal to | ||
168 | ifconfig the IP address and use that to ssh in. The root password is | ||
169 | empty, so to log in type 'root' for the user name and hit 'Enter' at | ||
170 | the Password prompt: and you should be in. | ||
171 | |||
172 | ---- | ||
173 | |||
174 | If you find you're getting corrupt images on the USB (it doesn't show | ||
175 | the syslinux boot: prompt, or the boot: prompt contains strange | ||
176 | characters), try doing this first: | ||
177 | |||
178 | # dd if=/dev/zero of=/dev/sdf bs=1M count=512 | ||