diff options
| author | Tom Zanussi <tom.zanussi@linux.intel.com> | 2013-01-24 15:19:36 -0600 |
|---|---|---|
| committer | Tom Zanussi <tom.zanussi@intel.com> | 2013-01-24 20:37:22 -0600 |
| commit | f9b9361eeb0bae697afc6db750bcfdbfbfe1a090 (patch) | |
| tree | 7127e7308c3d85f13dad7a24d8a6030c79bc20be /meta-emenlow | |
| parent | 229aa3f9a6e16b77437ee57856c9894435567acd (diff) | |
| download | meta-intel-f9b9361eeb0bae697afc6db750bcfdbfbfe1a090.tar.gz | |
emenlow: add LICENSE_FLAG_WHITELIST information to README
The switchover to emgd neglected to add the user documentation needed
for whitelisting the video components. This adds it and now matches
the other emgd-based BSPs.
Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
Diffstat (limited to 'meta-emenlow')
| -rw-r--r-- | meta-emenlow/README | 31 |
1 files changed, 27 insertions, 4 deletions
diff --git a/meta-emenlow/README b/meta-emenlow/README index 6cc06fe6..9487ff8c 100644 --- a/meta-emenlow/README +++ b/meta-emenlow/README | |||
| @@ -82,11 +82,14 @@ common metadata shared between BSPs) e.g.: | |||
| 82 | yocto/meta-intel \ | 82 | yocto/meta-intel \ |
| 83 | yocto/meta-intel/meta-emenlow \ | 83 | yocto/meta-intel/meta-emenlow \ |
| 84 | 84 | ||
| 85 | The meta-emenlow layer contains support for the 'emenlow' machine | 85 | The meta-emenlow layer contains support for two different machine |
| 86 | configuration, which makes use of the Intel-proprietary EMGD 1.16 | 86 | configurations. These configurations are identical except for the fact |
| 87 | graphics driver. | 87 | that the one prefixed with 'emenlow' makes use of the |
| 88 | Intel-proprietary EMGD 1.16 graphics driver, while the one prefixed | ||
| 89 | with 'emenlow-noemgd' does not. | ||
| 88 | 90 | ||
| 89 | To enable the emenlow layer, add the emenlow MACHINE to local.conf: | 91 | If you want to enable the layer that supports EMGD graphics add the |
| 92 | following to the local.conf file: | ||
| 90 | 93 | ||
| 91 | MACHINE ?= "emenlow" | 94 | MACHINE ?= "emenlow" |
| 92 | 95 | ||
| @@ -97,6 +100,11 @@ in your local.conf. For example: | |||
| 97 | 100 | ||
| 98 | LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.16" | 101 | LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.16" |
| 99 | 102 | ||
| 103 | If you want to enable the layer that does not support EMGD graphics | ||
| 104 | add the following to the local.conf file: | ||
| 105 | |||
| 106 | MACHINE ?= "emenlow-noemgd" | ||
| 107 | |||
| 100 | You should then be able to build an emenlow image as such: | 108 | You should then be able to build an emenlow image as such: |
| 101 | 109 | ||
| 102 | $ source oe-init-build-env | 110 | $ source oe-init-build-env |
| @@ -106,6 +114,21 @@ At the end of a successful build, you should have a live image that | |||
| 106 | you can boot from a USB flash drive (see instructions on how to do | 114 | you can boot from a USB flash drive (see instructions on how to do |
| 107 | that below, in the section 'Booting the images from /binary'). | 115 | that below, in the section 'Booting the images from /binary'). |
| 108 | 116 | ||
| 117 | NOTE: The 'emenlow' 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_emgd-driver-bin_1.16 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 | |||
| 109 | As an alternative to downloading the BSP tarball, you can also work | 132 | As an alternative to downloading the BSP tarball, you can also work |
| 110 | directly from the meta-intel git repository. For each BSP in the | 133 | directly from the meta-intel git repository. For each BSP in the |
| 111 | 'meta-intel' repository, there are multiple branches, one | 134 | 'meta-intel' repository, there are multiple branches, one |
