[meta-intel][fri2][PATCH] meta-fri2: update README to match current emgd driver version

[meta-intel][fri2][PATCH] meta-fri2: update README to match current emgd driver version

[Koen Kooi]

Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
---
 meta-fri2/README |    8 ++++----
 1 files changed, 4 insertions(+), 4 deletions(-)

diff --git a/meta-fri2/README b/meta-fri2/README
index af33c0b..b90613d 100644
--- a/meta-fri2/README
+++ b/meta-fri2/README
@@ -93,7 +93,7 @@ bblayers.conf, e.g.:
 The meta-fri2 layer contains support for two different machine
 configurations. These configurations are identical except for the fact
 that the one prefixed with 'fri2' makes use of the Intel-proprietary
-EMGD 1.10 graphics driver, while the one prefixed with 'fri2-noemgd'
+EMGD 1.14 graphics driver, while the one prefixed with 'fri2-noemgd'
 does not.
 
 If you want to enable the layer that supports EMGD graphics add the
@@ -103,10 +103,10 @@ following to the local.conf file:
 
 The 'fri2' machine includes the emgd-driver-bin package, which has a
 proprietary license that must be whitelisted by adding the string
-"license_emgd-driver-bin_1.10" to the LICENSE_FLAGS_WHITELIST variable
+"license_emgd-driver-bin_1.14" to the LICENSE_FLAGS_WHITELIST variable
 in your local.conf.  For example:
 
-  LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.10"
+  LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.14"
 
 If you want to enable the layer that does not support EMGD graphics
 add the following to the local.conf file:
@@ -128,7 +128,7 @@ added to the the LICENSE_FLAGS_WHITELIST variable in your local.conf.
 
 For example:
 
-  LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.10 commercial"
+  LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.14 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
-- 
1.7.7.6

Re: [meta-intel][fri2][PATCH] meta-fri2: update README to match current emgd driver version

[Darren Hart]

On 11/21/2012 06:43 AM, Koen Kooi wrote:

Nice catch Koen, thank you.

> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>
> ---
>  meta-fri2/README |    8 ++++----
>  1 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/meta-fri2/README b/meta-fri2/README
> index af33c0b..b90613d 100644
> --- a/meta-fri2/README
> +++ b/meta-fri2/README
> @@ -93,7 +93,7 @@ bblayers.conf, e.g.:
>  The meta-fri2 layer contains support for two different machine
>  configurations. These configurations are identical except for the fact
>  that the one prefixed with 'fri2' makes use of the Intel-proprietary
> -EMGD 1.10 graphics driver, while the one prefixed with 'fri2-noemgd'
> +EMGD 1.14 graphics driver, while the one prefixed with 'fri2-noemgd'
>  does not.
>  
>  If you want to enable the layer that supports EMGD graphics add the
> @@ -103,10 +103,10 @@ following to the local.conf file:
>  
>  The 'fri2' machine includes the emgd-driver-bin package, which has a
>  proprietary license that must be whitelisted by adding the string
> -"license_emgd-driver-bin_1.10" to the LICENSE_FLAGS_WHITELIST variable
> +"license_emgd-driver-bin_1.14" to the LICENSE_FLAGS_WHITELIST variable
>  in your local.conf.  For example:
>  
> -  LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.10"
> +  LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.14"
>  
>  If you want to enable the layer that does not support EMGD graphics
>  add the following to the local.conf file:
> @@ -128,7 +128,7 @@ added to the the LICENSE_FLAGS_WHITELIST variable in your local.conf.
>  
>  For example:
>  
> -  LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.10 commercial"
> +  LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.14 commercial"

I have taken to using:

LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin commercial"

Which avoids the constant updating based on version. Any objection to
using this instead of the version specific flag?

>  
>  The reason this is needed is to prevent the image from including
>  anything that might violate the license terms of the packages used to
> 

-- 
Darren Hart
Intel Open Source Technology Center
Yocto Project - Technical Lead - Linux Kernel

Re: [meta-intel][fri2][PATCH] meta-fri2: update README to match current emgd driver version

[Tom Zanussi]

On Wed, 2012-11-21 at 15:43 +0100, Koen Kooi wrote:
> Signed-off-by: Koen Kooi <koen@dominion.thruhere.net>

Pulled into meta-intel/master and meta-intel/danny-next.

Thanks,

Tom

> ---
>  meta-fri2/README |    8 ++++----
>  1 files changed, 4 insertions(+), 4 deletions(-)
> 
> diff --git a/meta-fri2/README b/meta-fri2/README
> index af33c0b..b90613d 100644
> --- a/meta-fri2/README
> +++ b/meta-fri2/README
> @@ -93,7 +93,7 @@ bblayers.conf, e.g.:
>  The meta-fri2 layer contains support for two different machine
>  configurations. These configurations are identical except for the fact
>  that the one prefixed with 'fri2' makes use of the Intel-proprietary
> -EMGD 1.10 graphics driver, while the one prefixed with 'fri2-noemgd'
> +EMGD 1.14 graphics driver, while the one prefixed with 'fri2-noemgd'
>  does not.
>  
>  If you want to enable the layer that supports EMGD graphics add the
> @@ -103,10 +103,10 @@ following to the local.conf file:
>  
>  The 'fri2' machine includes the emgd-driver-bin package, which has a
>  proprietary license that must be whitelisted by adding the string
> -"license_emgd-driver-bin_1.10" to the LICENSE_FLAGS_WHITELIST variable
> +"license_emgd-driver-bin_1.14" to the LICENSE_FLAGS_WHITELIST variable
>  in your local.conf.  For example:
>  
> -  LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.10"
> +  LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.14"
>  
>  If you want to enable the layer that does not support EMGD graphics
>  add the following to the local.conf file:
> @@ -128,7 +128,7 @@ added to the the LICENSE_FLAGS_WHITELIST variable in your local.conf.
>  
>  For example:
>  
> -  LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.10 commercial"
> +  LICENSE_FLAGS_WHITELIST = "license_emgd-driver-bin_1.14 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