diff options
| -rwxr-xr-x | meta-cedartrail/README | 15 | ||||
| -rw-r--r-- | meta-cedartrail/conf/machine/cedartrail.conf | 3 | ||||
| -rw-r--r-- | meta-chiefriver/README | 15 | ||||
| -rw-r--r-- | meta-chiefriver/conf/machine/chiefriver.conf | 3 | ||||
| -rw-r--r-- | meta-crownbay/README | 15 | ||||
| -rw-r--r-- | meta-crownbay/conf/machine/crownbay.conf | 3 | ||||
| -rw-r--r-- | meta-fri2/README | 15 | ||||
| -rw-r--r-- | meta-fri2/conf/machine/fri2.conf | 3 | ||||
| -rw-r--r-- | meta-sugarbay/README | 15 | ||||
| -rw-r--r-- | meta-sugarbay/conf/machine/sugarbay.conf | 3 | ||||
| -rw-r--r-- | meta-sys940x/README | 15 | ||||
| -rw-r--r-- | meta-sys940x/conf/machine/sys940x.conf | 3 |
12 files changed, 102 insertions, 6 deletions
diff --git a/meta-cedartrail/README b/meta-cedartrail/README index e47151e3..81a1260c 100755 --- a/meta-cedartrail/README +++ b/meta-cedartrail/README @@ -88,6 +88,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 'cedartrail' 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_cdv-pvr-driver_1.0.3 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 diff --git a/meta-cedartrail/conf/machine/cedartrail.conf b/meta-cedartrail/conf/machine/cedartrail.conf index cd9acd7c..33af0121 100644 --- a/meta-cedartrail/conf/machine/cedartrail.conf +++ b/meta-cedartrail/conf/machine/cedartrail.conf @@ -22,6 +22,7 @@ SYSLINUX_OPTS = "serial 0 115200" SERIAL_CONSOLE = "115200 ttyS0" APPEND += "console=ttyS0,115200 console=tty0" -VA_FEATURES ?= "gst-va-intel va-intel" +VA_FEATURES = "${@bb.utils.contains("LICENSE_FLAGS_WHITELIST", \ + "commercial", "gst-va-intel va-intel", "", d)}" MACHINE_EXTRA_RRECOMMENDS += "${VA_FEATURES}" diff --git a/meta-chiefriver/README b/meta-chiefriver/README index 49e44613..438c2930 100644 --- a/meta-chiefriver/README +++ b/meta-chiefriver/README @@ -60,6 +60,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 'chiefriver' 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 = "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 diff --git a/meta-chiefriver/conf/machine/chiefriver.conf b/meta-chiefriver/conf/machine/chiefriver.conf index 6d8d3a56..a9c8e5ac 100644 --- a/meta-chiefriver/conf/machine/chiefriver.conf +++ b/meta-chiefriver/conf/machine/chiefriver.conf @@ -15,6 +15,7 @@ XSERVER ?= "${XSERVER_IA32_BASE} \ ${XSERVER_IA32_I965} \ " -VA_FEATURES ?= "gst-va-intel va-intel" +VA_FEATURES = "${@bb.utils.contains("LICENSE_FLAGS_WHITELIST", \ + "commercial", "gst-va-intel va-intel", "", d)}" MACHINE_EXTRA_RRECOMMENDS += "${VA_FEATURES} lms" diff --git a/meta-crownbay/README b/meta-crownbay/README index 25214326..f7aeffac 100644 --- a/meta-crownbay/README +++ b/meta-crownbay/README @@ -92,6 +92,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 'crownbay' 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.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 +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 diff --git a/meta-crownbay/conf/machine/crownbay.conf b/meta-crownbay/conf/machine/crownbay.conf index c4b7682d..40dbd1d1 100644 --- a/meta-crownbay/conf/machine/crownbay.conf +++ b/meta-crownbay/conf/machine/crownbay.conf @@ -23,6 +23,7 @@ PREFERRED_VERSION_xf86-input-evdev ?= "2.6.0" APPEND += "video=vesafb vga=0x318" -VA_FEATURES ?= "gst-va-intel va-intel" +VA_FEATURES = "${@bb.utils.contains("LICENSE_FLAGS_WHITELIST", \ + "commercial", "gst-va-intel va-intel", "va-intel", d)}" MACHINE_EXTRA_RRECOMMENDS += "${VA_FEATURES}" diff --git a/meta-fri2/README b/meta-fri2/README index 2208392f..a8661744 100644 --- a/meta-fri2/README +++ b/meta-fri2/README @@ -113,6 +113,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 'fri2' 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.10 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 diff --git a/meta-fri2/conf/machine/fri2.conf b/meta-fri2/conf/machine/fri2.conf index 56408f7e..bf7754fc 100644 --- a/meta-fri2/conf/machine/fri2.conf +++ b/meta-fri2/conf/machine/fri2.conf @@ -8,7 +8,8 @@ require conf/machine/include/tune-atom.inc require conf/machine/include/ia32-base.inc require conf/machine/include/meta-intel.inc -VA_FEATURES ?= "gst-va-intel va-intel" +VA_FEATURES = "${@bb.utils.contains("LICENSE_FLAGS_WHITELIST", \ + "commercial", "gst-va-intel va-intel", "va-intel", d)}" MACHINE_FEATURES += "wifi 3g pcbios efi va-impl-mixvideo" MACHINE_EXTRA_RRECOMMENDS += "linux-firmware-iwlwifi-6000g2a-5 ${VA_FEATURES}" diff --git a/meta-sugarbay/README b/meta-sugarbay/README index 413b2ab8..80833c1e 100644 --- a/meta-sugarbay/README +++ b/meta-sugarbay/README @@ -71,6 +71,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 'sugarbay' 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 = "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 diff --git a/meta-sugarbay/conf/machine/sugarbay.conf b/meta-sugarbay/conf/machine/sugarbay.conf index 616c2c5b..17cc15ca 100644 --- a/meta-sugarbay/conf/machine/sugarbay.conf +++ b/meta-sugarbay/conf/machine/sugarbay.conf @@ -16,6 +16,7 @@ XSERVER ?= "${XSERVER_IA32_BASE} \ ${XSERVER_IA32_I965} \ " -VA_FEATURES ?= "gst-va-intel va-intel" +VA_FEATURES = "${@bb.utils.contains("LICENSE_FLAGS_WHITELIST", \ + "commercial", "gst-va-intel va-intel", "", d)}" MACHINE_EXTRA_RRECOMMENDS += "${VA_FEATURES}" diff --git a/meta-sys940x/README b/meta-sys940x/README index b030faf5..90589375 100644 --- a/meta-sys940x/README +++ b/meta-sys940x/README @@ -96,6 +96,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 'sys940x' 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.10 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 diff --git a/meta-sys940x/conf/machine/sys940x.conf b/meta-sys940x/conf/machine/sys940x.conf index 9db2b2a4..f71bb3a8 100644 --- a/meta-sys940x/conf/machine/sys940x.conf +++ b/meta-sys940x/conf/machine/sys940x.conf @@ -25,6 +25,7 @@ PREFERRED_VERSION_xf86-input-evdev ?= "2.6.0" SERIAL_CONSOLE = "115200 ttyS0" APPEND += "console=ttyS0,115200 console=tty0" -VA_FEATURES ?= "gst-va-intel va-intel" +VA_FEATURES = "${@bb.utils.contains("LICENSE_FLAGS_WHITELIST", \ + "commercial", "gst-va-intel va-intel", "va-intel", d)}" MACHINE_EXTRA_RRECOMMENDS += "${VA_FEATURES}" |