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