diff options
Diffstat (limited to 'meta-crownbay/README')
-rw-r--r-- | meta-crownbay/README | 51 |
1 files changed, 6 insertions, 45 deletions
diff --git a/meta-crownbay/README b/meta-crownbay/README index 1946d3e1..d0d9fe6d 100644 --- a/meta-crownbay/README +++ b/meta-crownbay/README | |||
@@ -5,9 +5,6 @@ Please see the corresponding sections below for details. | |||
5 | The Crown Bay platform consists of the Intel Atom E6xx processor, | 5 | The Crown Bay platform consists of the Intel Atom E6xx processor, |
6 | plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff). | 6 | plus the Intel EG20T Platform Controller Hub (Tunnel Creek + Topcliff). |
7 | 7 | ||
8 | It also supports the E6xx embedded on-chip graphics via the Intel | ||
9 | Embedded Media and Graphics Driver (EMGD) 1.18 Driver. | ||
10 | |||
11 | Further information on the platforms supported by this BSP can be | 8 | Further information on the platforms supported by this BSP can be |
12 | found here: | 9 | found here: |
13 | 10 | ||
@@ -78,33 +75,12 @@ common metadata shared between BSPs) e.g.: | |||
78 | yocto/meta-intel \ | 75 | yocto/meta-intel \ |
79 | yocto/meta-intel/meta-crownbay \ | 76 | yocto/meta-intel/meta-crownbay \ |
80 | 77 | ||
81 | The meta-crownbay layer contains support for two different machine | 78 | The meta-crownbay layer contains support for the crownbay-noemgd machine |
82 | configurations. These configurations are identical except for the fact | 79 | configuration. The previously supported crownbay machine with the |
83 | that the one prefixed with 'crownbay' makes use of the | 80 | proprietary EMGD graphics driver has been retired. The 'crownbay-noemgd' |
84 | Intel-proprietary EMGD 1.18 graphics driver, while the one prefixed | 81 | machine configuration uses the open source 'vesa' kernel driver. |
85 | with 'crownbay-noemgd' does not. | ||
86 | |||
87 | If you want to enable the layer that supports EMGD graphics add the | ||
88 | following to the local.conf file: | ||
89 | |||
90 | MACHINE ?= "crownbay" | ||
91 | |||
92 | The 'crownbay' machine includes the emgd-driver-bin package, which has | ||
93 | a proprietary license that must be whitelisted by adding the string | ||
94 | "license_emgd-driver-bin_1.18" to the LICENSE_FLAGS_WHITELIST variable | ||
95 | in your local.conf. For example: | ||
96 | |||
97 | LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin" | ||
98 | |||
99 | The emgd recipe depends on Xorg's dri and glx modules, which are built | ||
100 | only when 'opengl' is listed in DISTRO_FEATURES. So if the distro | ||
101 | doesn't list 'opengl' in the DISTRO_FEATURES you would need this | ||
102 | additional line to your local.conf: | ||
103 | 82 | ||
104 | DISTRO_FEATURES_append = " opengl" | 83 | To enable the layer add the following to the local.conf file: |
105 | |||
106 | If you want to enable the layer that does not support EMGD graphics | ||
107 | add the following to the local.conf file: | ||
108 | 84 | ||
109 | MACHINE ?= "crownbay-noemgd" | 85 | MACHINE ?= "crownbay-noemgd" |
110 | 86 | ||
@@ -117,21 +93,6 @@ At the end of a successful build, you should have a live image that | |||
117 | you can boot from a USB flash drive (see instructions on how to do | 93 | you can boot from a USB flash drive (see instructions on how to do |
118 | that below, in the section 'Booting the images from /binary'). | 94 | that below, in the section 'Booting the images from /binary'). |
119 | 95 | ||
120 | NOTE: The 'crownbay' machine will include support for hardware video | ||
121 | acceleration via gstreamer if and only if the "commercial" string is | ||
122 | added to the the LICENSE_FLAGS_WHITELIST variable in your local.conf. | ||
123 | |||
124 | For example: | ||
125 | |||
126 | LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial" | ||
127 | |||
128 | The reason this is needed is to prevent the image from including | ||
129 | anything that might violate the license terms of the packages used to | ||
130 | implement the the video acceleration feature, such as gst-ffmpeg and | ||
131 | ffmpeg. As always, please consult the licenses included in the | ||
132 | specific packages for details if you use packages that require | ||
133 | particular LICENSE_FLAGS. | ||
134 | |||
135 | As an alternative to downloading the BSP tarball, you can also work | 96 | As an alternative to downloading the BSP tarball, you can also work |
136 | directly from the meta-intel git repository. For each BSP in the | 97 | directly from the meta-intel git repository. For each BSP in the |
137 | 'meta-intel' repository, there are multiple branches, one | 98 | 'meta-intel' repository, there are multiple branches, one |
@@ -153,7 +114,7 @@ Under Linux, insert a USB flash drive. Assuming the USB flash drive | |||
153 | takes device /dev/sdf, use dd to copy the live image to it. For | 114 | takes device /dev/sdf, use dd to copy the live image to it. For |
154 | example: | 115 | example: |
155 | 116 | ||
156 | # dd if=core-image-sato-crownbay.hddimg of=/dev/sdf | 117 | # dd if=core-image-sato-crownbay-noemgd.hddimg of=/dev/sdf |
157 | # sync | 118 | # sync |
158 | # eject /dev/sdf | 119 | # eject /dev/sdf |
159 | 120 | ||