[meta-intel] [PATCH 1/1] emenlow: add LICENSE_FLAG_WHITELIST information to README

Kamble, Nitin A nitin.a.kamble at intel.com
Thu Jan 24 17:06:41 PST 2013


Tom,
    The information about emenlow-noemgd BSP is also missing in the
README. Can you take care of that also in this commit?

Thanks,
Nitin


> -----Original Message-----
> From: meta-intel-bounces at yoctoproject.org [mailto:meta-intel-
> bounces at yoctoproject.org] On Behalf Of tom.zanussi at linux.intel.com
> Sent: Thursday, January 24, 2013 1:35 PM
> To: meta-intel at yoctoproject.org
> Cc: Tom Zanussi
> Subject: [meta-intel] [PATCH 1/1] emenlow: add LICENSE_FLAG_WHITELIST
> information to README
> 
> From: Tom Zanussi <tom.zanussi at linux.intel.com>
> 
> 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 at linux.intel.com>
> ---
>  meta-emenlow/README | 15 +++++++++++++++
>  1 file changed, 15 insertions(+)
> 
> diff --git a/meta-emenlow/README b/meta-emenlow/README index
> 6cc06fe..245b178 100644
> --- a/meta-emenlow/README
> +++ b/meta-emenlow/README
> @@ -106,6 +106,21 @@ At the end of a successful build, you should have a
> live image that  you can boot from a USB flash drive (see instructions on how
> to do  that below, in the section 'Booting the images from /binary').
> 
> +NOTE: The 'emenlow' machine will include support for hardware video
> +acceleration via gstreamer if and only if the "commercial" string is
> +added to the the LICENSE_FLAGS_WHITELIST variable in your local.conf.
> +
> +For example:
> +
> +  LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.16 commercial"
> +
> +The reason this is needed is to prevent the image from including
> +anything that might violate the license terms of the packages used to
> +implement the the video acceleration feature, such as gst-ffmpeg and
> +ffmpeg.  As always, please consult the licenses included in the
> +specific packages for details if you use packages that require
> +particular LICENSE_FLAGS.
> +
>  As an alternative to downloading the BSP tarball, you can also work  directly
> from the meta-intel git repository.  For each BSP in the  'meta-intel'
> repository, there are multiple branches, one
> --
> 1.7.11.4
> 
> _______________________________________________
> meta-intel mailing list
> meta-intel at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-intel



More information about the meta-intel mailing list