date:20150811

Re: [meta-intel] [fido][PATCH 1/1] common/linux-yocto_3.14: update meta branch SRCREV

2015-08-11 Thread Wu, Chia Chuan



> -Original Message-
> From: Darren Hart [mailto:dvh...@linux.intel.com]
> Sent: Thursday, August 6, 2015 7:17 AM
> To: Wu, Chia Chuan 
> Cc: meta-intel@yoctoproject.org
> Subject: Re: [meta-intel] [fido][PATCH 1/1] common/linux-yocto_3.14: update
> meta branch SRCREV
> 
> On 8/3/15 3:03 AM, chia.chuan...@intel.com wrote:
> > From: Wu Chia Chuan 
> >
> > Enable i40e network driver for Intel Ethernet Controller XL710/X710 on
> > Intel common BSP so that the NIC card is discoverable under River Forest
> platform.
> >
> 
> This fails to apply to master, and we don't apply patches to fido that haven't
> been first applied to master.
> 
> Please develop against master and request backports to the stable branches.
Darren, linux-yocto meta branch was separated out in master branch and pointing 
 
to " yocto-kernel-cache" repo. Fido branch still use the meta branch from 
"linux-yocto-3.xx" repo, the revisions would not be common for the two branches.

This patch is required for River Forest BSP ,which is developed/tested under 
fido branch.
> 
> --
> Darren Hart
> Intel Open Source Technology Center
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

[meta-intel] [PATCH 2/3] libva: upgrade to 1.6.0 (v2)

2015-08-11 Thread Lim Siew Hoon

The libva-intel-driver 1.6.0 version got dependecy to libva 1.6.0
VA-API 0.38 version.

For Gen9 platform support.

Signed-off-by: Lim Siew Hoon 
---
 common/recipes-multimedia/libva/{libva_1.5.0.bb => libva_1.6.0.bb} | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
 rename common/recipes-multimedia/libva/{libva_1.5.0.bb => libva_1.6.0.bb} (93%)
 mode change 100644 => 100755

diff --git a/common/recipes-multimedia/libva/libva_1.5.0.bb 
b/common/recipes-multimedia/libva/libva_1.6.0.bb
old mode 100644
new mode 100755
similarity index 93%
rename from common/recipes-multimedia/libva/libva_1.5.0.bb
rename to common/recipes-multimedia/libva/libva_1.6.0.bb
index 85fe4cd..bfce3c4
--- a/common/recipes-multimedia/libva/libva_1.5.0.bb
+++ b/common/recipes-multimedia/libva/libva_1.6.0.bb
@@ -18,8 +18,8 @@ LICENSE = "MIT"
 LIC_FILES_CHKSUM = "file://COPYING;md5=2e48940f94acb0af582e5ef03537800f"
 
 SRC_URI = 
"http://www.freedesktop.org/software/vaapi/releases/libva/${BP}.tar.bz2";
-SRC_URI[md5sum] = "ad0b55794308ec397d249a0a2a6df27a"
-SRC_URI[sha256sum] = 
"e946d4b3110e4e23ec6a588e0c828937e502c67196d1266214441fefc4b83486"
+SRC_URI[md5sum] = "3f1241b4080db53c120325932f393f33"
+SRC_URI[sha256sum] = 
"3ad9dc9c1a6a10e9cc4234c2a1cd5e568ec0cd25145e86875eba6e0d69153458"
 
 DEPENDS = "libdrm virtual/mesa virtual/libgles1 virtual/libgles2 virtual/egl"
 
-- 
2.1.0

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

[meta-intel] [PATCH 1/3] gstreamer-vaapi: upgrade to 0.6.0 (v2)

2015-08-11 Thread Lim Siew Hoon

Request gstreamer-vaapi upgrade for Gen9 platform support.
Tested with some video clip format in H265, H264, VC1, HEVC,
JPEG, MPEG2, VP8 decode on CHV platform as well.

Gstreamer support corner from gstreamer-vaapi release note:
- Removed the support for Gstreamer 0.10 and 1.0.
- Gstreamer >= 1.2 the minimal requirement.

Add in the dependedcy libva-intel-driver in gstreamer-vaapi.inc.
Because gstreamer-vaapi depend to libva-intel-driver as well not just
only libva.

Fixed the compilation error causing by the install test patch

Signed-off-by: Lim Siew Hoon 
---
 ...-1.0_0.5.10.bb => gstreamer-vaapi-1.0_0.6.0.bb} |  0
 .../gstreamer/gstreamer-vaapi.inc  |  6 ++--
 .../gstreamer/gstreamer-vaapi/install-tests.patch  | 35 ++
 3 files changed, 32 insertions(+), 9 deletions(-)
 rename common/recipes-multimedia/gstreamer/{gstreamer-vaapi-1.0_0.5.10.bb => 
gstreamer-vaapi-1.0_0.6.0.bb} (100%)
 mode change 100644 => 100755

diff --git a/common/recipes-multimedia/gstreamer/gstreamer-vaapi-1.0_0.5.10.bb 
b/common/recipes-multimedia/gstreamer/gstreamer-vaapi-1.0_0.6.0.bb
old mode 100644
new mode 100755
similarity index 100%
rename from common/recipes-multimedia/gstreamer/gstreamer-vaapi-1.0_0.5.10.bb
rename to common/recipes-multimedia/gstreamer/gstreamer-vaapi-1.0_0.6.0.bb
diff --git a/common/recipes-multimedia/gstreamer/gstreamer-vaapi.inc 
b/common/recipes-multimedia/gstreamer/gstreamer-vaapi.inc
index 64c6131..20a17a4 100644
--- a/common/recipes-multimedia/gstreamer/gstreamer-vaapi.inc
+++ b/common/recipes-multimedia/gstreamer/gstreamer-vaapi.inc
@@ -9,14 +9,14 @@ FILESPATH = 
"${@base_set_filespath(["${FILE_DIRNAME}/${REALPN}", "${FILE_DIRNAME
 LICENSE = "LGPLv2.1+"
 LIC_FILES_CHKSUM = "file://COPYING.LIB;md5=4fbd65380cdd255951079008b364516c"
 
-DEPENDS = "libva"
+DEPENDS = "libva libva-intel-driver"
 
 SRC_URI = 
"http://www.freedesktop.org/software/vaapi/releases/${REALPN}/${REALPN}-${PV}.tar.bz2
 \
file://install-tests.patch \
"
 
-SRC_URI[md5sum] = "3bd90b696b644be943450ba0c1497193"
-SRC_URI[sha256sum] = 
"0dd236c7bf225322b8934fdba99a7a9e4542566a2acbe7564cdc3ec2c8b73c9d"
+SRC_URI[md5sum] = "c8d8ba19d7d18d9e7bd455f73bb5daf2"
+SRC_URI[sha256sum] = 
"f6a4c657606849fb09ee2db778c80278cfa4546e9103862f273c910e208872b8"
 
 S = "${WORKDIR}/${REALPN}-${PV}"
 
diff --git 
a/common/recipes-multimedia/gstreamer/gstreamer-vaapi/install-tests.patch 
b/common/recipes-multimedia/gstreamer/gstreamer-vaapi/install-tests.patch
index 9281b04..7ebbb1b 100644
--- a/common/recipes-multimedia/gstreamer/gstreamer-vaapi/install-tests.patch
+++ b/common/recipes-multimedia/gstreamer/gstreamer-vaapi/install-tests.patch
@@ -1,14 +1,30 @@
-Install tests.
+From 0c915a620ac4f1f679cca21363f4e083812e42d0 Mon Sep 17 00:00:00 2001
+From: Lim Siew Hoon 
+Date: Wed, 22 Jul 2015 18:18:15 +0800
+Subject: [PATCH] install tests.
 
 Upstream-Status: Inappropriate
 Signed-off-by: Ross Burton 
 
+This patch was imported from the meta-intel git server
+(git://git.yoctoproject.org/meta-intel) as of commit id
+ccc27afc38d0190e25d7c19ebb49d5c33fba3194.
+
+A previous change had modified the test as get install
+into the system causing compilation error after apply into
+gstreamer-vaapi 0.6.0. This is due to the test under if USE_GLX
+'noinst_PROGRAMS +=' didn't replaced with 'bin_PROGRAMS +='.
+The compilation error was resolved by replaced the miss out
+'noinst_PROGRAMS +=' to 'bin_PROGRAMS +=' from existing
+implementation.
+
+Signed-off-by: Lim Siew Hoon 
 ---
- tests/Makefile.am |4 ++--
- 1 file changed, 2 insertions(+), 2 deletions(-)
+ tests/Makefile.am | 6 +++---
+ 1 file changed, 3 insertions(+), 3 deletions(-)
 
 diff --git a/tests/Makefile.am b/tests/Makefile.am
-index 2e7f191..8f65446 100644
+index 3637d92..7cc6a97 100644
 --- a/tests/Makefile.am
 +++ b/tests/Makefile.am
 @@ -1,4 +1,4 @@
@@ -17,9 +33,16 @@ index 2e7f191..8f65446 100644
simple-decoder  \
test-decode \
test-display\
-@@ -9,7 +9,7 @@ noinst_PROGRAMS = \
+@@ -9,13 +9,13 @@ noinst_PROGRAMS = \
$(NULL)
  
+ if USE_ENCODERS
+-noinst_PROGRAMS += \
++bin_PROGRAMS += \
+   simple-encoder  \
+   $(NULL)
+ endif
+ 
  if USE_GLX
 -noinst_PROGRAMS += \
 +bin_PROGRAMS += \
@@ -27,5 +50,5 @@ index 2e7f191..8f65446 100644
$(NULL)
  endif
 -- 
-1.7.10.4
+2.1.0
 
-- 
2.1.0

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

[meta-intel] [PATCH 3/3] libva-intel-driver: Upgrade to 1.6.0 (v2)

2015-08-11 Thread Lim Siew Hoon

For Gen9 platform support.
Tested with running some H264, H265, MPEG2, JPEG, VC1, VP8, MJPEG decode
in CHV and SKL platform.

Clean up:
Remove wayland-include.patch, code already exist in 1.6.0 version.

Add in patch:
Fix GPU hung issue patch causing by running H264 video clip with MBAFF.

Signed-off-by: Lim Siew Hoon 
---
 ...croblock-pair-to-calculate-H264-decoding-.patch | 141 +
 .../libva/libva-intel-driver/wayland-include.patch |  30 -
 ...driver_1.5.0.bb => libva-intel-driver_1.6.0.bb} |   9 +-
 3 files changed, 146 insertions(+), 34 deletions(-)
 create mode 100644 
common/recipes-multimedia/libva/libva-intel-driver/0001-H264-Use-macroblock-pair-to-calculate-H264-decoding-.patch
 delete mode 100644 
common/recipes-multimedia/libva/libva-intel-driver/wayland-include.patch
 rename common/recipes-multimedia/libva/{libva-intel-driver_1.5.0.bb => 
libva-intel-driver_1.6.0.bb} (78%)
 mode change 100644 => 100755

diff --git 
a/common/recipes-multimedia/libva/libva-intel-driver/0001-H264-Use-macroblock-pair-to-calculate-H264-decoding-.patch
 
b/common/recipes-multimedia/libva/libva-intel-driver/0001-H264-Use-macroblock-pair-to-calculate-H264-decoding-.patch
new file mode 100644
index 000..fd5da79
--- /dev/null
+++ 
b/common/recipes-multimedia/libva/libva-intel-driver/0001-H264-Use-macroblock-pair-to-calculate-H264-decoding-.patch
@@ -0,0 +1,141 @@
+From bdda6233e212e74f6d348b55906433126324130b Mon Sep 17 00:00:00 2001
+From: Zhao Yakui 
+Date: Tue, 7 Jul 2015 01:45:47 +0800
+Subject: [PATCH] H264: Use macroblock pair to calculate H264 decoding
+ parameter under MBAFF flag
+
+Based on the H264 spec the macroblock pair should be used to calculate
+the corresponding parameters under MBAFF.(mb-adaptive frame-field).
+Otherwise the wrong parameter is sent to GPU HW.
+
+Fix the GPU hang issue in https://bugs.freedesktop.org/show_bug.cgi?id=91207
+
+Tested-by: Lim, Siew Hoon 
+Signed-off-by: Zhao Yakui 
+
+Upstream-status: backport from upstream
+This patch was imported from the Intel VA Driver git server
+(git://anongit.freedesktop.org/vaapi/intel-driver) as of commit id
+7bb3658212f49a6f8d3d61b0b5d161aca73c2a11.
+
+This issue caught by running some H264 video under MBAFF flag, it happen in
+HSW, IVY, CHV, SKL platform as well.
+
+Signed-off-by: Lim, Siew Hoon 
+---
+ src/gen6_mfd.c  | 10 --
+ src/gen75_mfd.c | 10 --
+ src/gen7_mfd.c  | 10 --
+ src/gen8_mfd.c  |  9 +++--
+ 4 files changed, 31 insertions(+), 8 deletions(-)
+
+diff --git a/src/gen6_mfd.c b/src/gen6_mfd.c
+index 95a8e92..2dd05a1 100755
+--- a/src/gen6_mfd.c
 b/src/gen6_mfd.c
+@@ -551,14 +551,20 @@ gen6_mfd_avc_slice_state(VADriverContextP ctx,
+ }
+ }
+ 
+-first_mb_in_slice = slice_param->first_mb_in_slice << mbaff_picture;
++first_mb_in_slice = slice_param->first_mb_in_slice;
+ slice_hor_pos = first_mb_in_slice % width_in_mbs; 
+ slice_ver_pos = first_mb_in_slice / width_in_mbs;
+ 
++if (mbaff_picture)
++slice_ver_pos = slice_ver_pos << 1;
++
+ if (next_slice_param) {
+-first_mb_in_next_slice = next_slice_param->first_mb_in_slice << 
mbaff_picture;
++first_mb_in_next_slice = next_slice_param->first_mb_in_slice;
+ next_slice_hor_pos = first_mb_in_next_slice % width_in_mbs; 
+ next_slice_ver_pos = first_mb_in_next_slice / width_in_mbs;
++
++if (mbaff_picture)
++next_slice_ver_pos = next_slice_ver_pos << 1;
+ } else {
+ next_slice_hor_pos = 0;
+ next_slice_ver_pos = height_in_mbs;
+diff --git a/src/gen75_mfd.c b/src/gen75_mfd.c
+index 5171bd9..11cde1f 100644
+--- a/src/gen75_mfd.c
 b/src/gen75_mfd.c
+@@ -862,14 +862,20 @@ gen75_mfd_avc_slice_state(VADriverContextP ctx,
+ num_ref_idx_l1 = slice_param->num_ref_idx_l1_active_minus1 + 1;
+ }
+ 
+-first_mb_in_slice = slice_param->first_mb_in_slice << mbaff_picture;
++first_mb_in_slice = slice_param->first_mb_in_slice;
+ slice_hor_pos = first_mb_in_slice % width_in_mbs; 
+ slice_ver_pos = first_mb_in_slice / width_in_mbs;
+ 
++if (mbaff_picture)
++slice_ver_pos = slice_ver_pos << 1;
++
+ if (next_slice_param) {
+-first_mb_in_next_slice = next_slice_param->first_mb_in_slice << 
mbaff_picture;
++first_mb_in_next_slice = next_slice_param->first_mb_in_slice;
+ next_slice_hor_pos = first_mb_in_next_slice % width_in_mbs; 
+ next_slice_ver_pos = first_mb_in_next_slice / width_in_mbs;
++
++if (mbaff_picture)
++next_slice_ver_pos = next_slice_ver_pos << 1;
+ } else {
+ next_slice_hor_pos = 0;
+ next_slice_ver_pos = height_in_mbs / (1 + 
!!pic_param->pic_fields.bits.field_pic_flag);
+diff --git a/src/gen7_mfd.c b/src/gen7_mfd.c
+index 40a6db4..1d04ed4 100755
+--- a/src/gen7_mfd.c
 b/src/gen7_mfd.c
+@@ -556,14 +556,20 @@ gen7_mfd_avc_slice_state(VADriverContextP ctx,
+ num_ref_idx_l1 = slice_param->num_ref_idx_l1_a

[meta-intel] [PATCH 0/3] Upgrade gstreamer-vaapi, libva & Intel VA driver

2015-08-11 Thread Lim Siew Hoon

Those patch are target using for Gen9 platform support.

To upgrade Intel-VA driver to 1.6.0, it also needs to upgrade together with
libva 1.6.0. Because Intel-VA driver got dependecy with VA-API version 0.38,
this VA-API version only bump libva 1.6.0.

Upgrade the gstreamer-vaapi to 0.6.0 for new feature add HEVC encode.
(But I haven't test it yet.)

Tested with video decode in video format H264, HEVC, VC1, MPEG2,
JPEG/MJPEG, VP8 decode in BSW and SKL platform.

Lim Siew Hoon (3):
  gstreamer-vaapi: upgrade to 0.6.0 (v2)
  libva: upgrade to 1.6.0 (v2)
  libva-intel-driver: Upgrade to 1.6.0 (v2)

Zhao, Yakui (1):
  0001-H264-Use-macroblock-pair-to-calculate-H264-decoding-.patch
  (Part of libva-intel-driver: Upgrade to 1.6.0 patch)

 ...-1.0_0.5.10.bb => gstreamer-vaapi-1.0_0.6.0.bb} |   0
 .../gstreamer/gstreamer-vaapi.inc  |   6 +-
 .../gstreamer/gstreamer-vaapi/install-tests.patch  |  35 -
 ...croblock-pair-to-calculate-H264-decoding-.patch | 141 +
 .../libva/libva-intel-driver/wayland-include.patch |  30 -
 ...driver_1.5.0.bb => libva-intel-driver_1.6.0.bb} |   9 +-
 .../libva/{libva_1.5.0.bb => libva_1.6.0.bb}   |   4 +-
 7 files changed, 180 insertions(+), 45 deletions(-)
 rename common/recipes-multimedia/gstreamer/{gstreamer-vaapi-1.0_0.5.10.bb => 
gstreamer-vaapi-1.0_0.6.0.bb} (100%)
 mode change 100644 => 100755
 create mode 100644 
common/recipes-multimedia/libva/libva-intel-driver/0001-H264-Use-macroblock-pair-to-calculate-H264-decoding-.patch
 delete mode 100644 
common/recipes-multimedia/libva/libva-intel-driver/wayland-include.patch
 rename common/recipes-multimedia/libva/{libva-intel-driver_1.5.0.bb => 
libva-intel-driver_1.6.0.bb} (78%)
 mode change 100644 => 100755
 rename common/recipes-multimedia/libva/{libva_1.5.0.bb => libva_1.6.0.bb} (93%)
 mode change 100644 => 100755

-- 
2.1.0

-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH 1/3] gstreamer-vaapi: upgrade to 0.6.0 (v2)

2015-08-11 Thread Burton, Ross

On 11 August 2015 at 11:49, Lim Siew Hoon  wrote:

> +DEPENDS = "libva libva-intel-driver"
>

Is that an actual build dependency?  If it's a runtime dependency then you
mean RDEPENDS, and isn't gstreamer-vaapi driver-agnostic (although mainly
tested against the Intel driver)?

Ross
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH 1/3] gstreamer-vaapi: upgrade to 0.6.0 (v2)

2015-08-11 Thread Lim, Siew Hoon

> From: Burton, Ross [mailto:ross.bur...@intel.com] 
> Sent: Tuesday, August 11, 2015 7:15 PM
> To: Lim, Siew Hoon
> Cc: meta-intel@yoctoproject.org; Ho, Nee Shen
> Subject: Re: [meta-intel] [PATCH 1/3] gstreamer-vaapi: upgrade to 0.6.0 (v2)

> On 11 August 2015 at 11:49, Lim Siew Hoon  wrote:
> +DEPENDS = "libva libva-intel-driver"

> Is that an actual build dependency?  If it's a runtime dependency then you 
> mean RDEPENDS, and isn't gstreamer-vaapi driver-agnostic (although mainly 
> tested against the Intel driver)?

Based on experience, it is better build and install the gstreamer-vaapi after 
libva and libva-intel-driver get install first. 
Sometime it will screw up (video playback with corruption or performance) if we 
didn't follow the sequence this experience in others OS distribution. 

If you think don't need then I can take out. But I just want to make sure 
gstreamer-vaapi is built after libva-intel-driver get install in yocto. 
Question how do I check the gstreamer-vaapi is built after libva-intel-driver?

Build and install sequence: libva -> libva-intel-driver -> gstreamer-vaapi.

Thanks.
...siewhoon

> Ross
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

[meta-intel] Do we still need GST_API_VERSION inside gstreamer-vaapi-xxx.bb recipes?

2015-08-11 Thread Lim, Siew Hoon

Hi Ross,

Why we need to add GST_API_VERSION?  Do we really still need it? 

Gstreamer-vaapi already include those GST_API_VERSION checking in 
configuration.ac which gstreamer framework version support.
And --with-gstreamer-api option also didn't exist in gstreamer-vaapi. 

Will get this kind of warning message:
WARNING: QA Issue: gstreamer-vaapi-1.0: configure was passed unrecognised 
options: --with-gstreamer-api [unknown-configure-option]


Can we do a cleanup for it? 
1. Remove out --with-gstreamer-api=${GST_API_VERSION} inside the 
gstreamer-vaapi.inc?
2. Remove out the GST_API_VERSION from gstreamer-vaapi recipes?

Thanks.
.siewhoon


-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH 1/3] gstreamer-vaapi: upgrade to 0.6.0 (v2)

2015-08-11 Thread Jussi Kukkonen

On 11 August 2015 at 15:15, Lim, Siew Hoon  wrote:
>
>> From: Burton, Ross [mailto:ross.bur...@intel.com]
>> Sent: Tuesday, August 11, 2015 7:15 PM
>> To: Lim, Siew Hoon
>> Cc: meta-intel@yoctoproject.org; Ho, Nee Shen
>> Subject: Re: [meta-intel] [PATCH 1/3] gstreamer-vaapi: upgrade to 0.6.0 (v2)
>
>
>> On 11 August 2015 at 11:49, Lim Siew Hoon  wrote:
>> +DEPENDS = "libva libva-intel-driver"
>
>> Is that an actual build dependency?  If it's a runtime dependency then you 
>> mean RDEPENDS, and isn't gstreamer-vaapi driver-agnostic (although mainly 
>> tested against the Intel driver)?
>
> Based on experience, it is better build and install the gstreamer-vaapi after 
> libva and libva-intel-driver get install first.
> Sometime it will screw up (video playback with corruption or performance) if 
> we didn't follow the sequence this experience in others OS distribution.

How could the intel driver affect how gstreamer-vaapi is built? That
sounds like it would be a gstreamer-vaapi bug if true.

 - Jussi

> If you think don't need then I can take out. But I just want to make sure 
> gstreamer-vaapi is built after libva-intel-driver get install in yocto.
> Question how do I check the gstreamer-vaapi is built after libva-intel-driver?
>
> Build and install sequence: libva -> libva-intel-driver -> gstreamer-vaapi.
>
> Thanks.
> ...siewhoon
>
>
>> Ross
> --
> ___
> meta-intel mailing list
> meta-intel@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-intel
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] Do we still need GST_API_VERSION inside gstreamer-vaapi-xxx.bb recipes?

2015-08-11 Thread Burton, Ross

On 11 August 2015 at 13:29, Lim, Siew Hoon  wrote:

> Why we need to add GST_API_VERSION?  Do we really still need it?
>
> Gstreamer-vaapi already include those GST_API_VERSION checking in
> configuration.ac which gstreamer framework version support.
> And --with-gstreamer-api option also didn't exist in gstreamer-vaapi.
>
> Will get this kind of warning message:
> WARNING: QA Issue: gstreamer-vaapi-1.0: configure was passed unrecognised
> options: --with-gstreamer-api [unknown-configure-option]
>
>
> Can we do a cleanup for it?
> 1. Remove out --with-gstreamer-api=${GST_API_VERSION} inside the
> gstreamer-vaapi.inc?
> 2. Remove out the GST_API_VERSION from gstreamer-vaapi recipes?
>

It was needed in the past when there were both 0.10 and 1.0 recipes for
gstreamer-vaapi, but if gstreamer-vaapi has removed the
--with-gstreamer-api option then it can all be deleted.

Ross
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH V2] intel-gpu-tools: upgrade to version 1.11

2015-08-11 Thread Saul Wold


On 08/10/2015 10:08 PM, Pengyu Ma wrote:

Disable gtk-doc to fix building error.
Add libunwind package config to fix denpendece.

Changes since v1:
  * Add libunwind package config.


During my testing of this, I saw the following warning:

WARNING: QA Issue: 
/usr/lib/intel-gpu-tools/intel-gpu-tools/tools@underscore@test_intel-gpu-tools 
contained in package intel-gpu-tools requires /bin/bash, but no providers found 
in its RDEPENDS [file-rdeps]


It seems that some script in this package requires bash, is it possible 
to remove the bashism and use the standard "/bin/sh" instead?


Also, did you do a remove and recreate of the recipe or a "git mv" 
Normally we do a git mv and then can clearly see the difference between 
the 2 versions as git will handle the move easier.


Thanks
Sau!


Signed-off-by: Pengyu Ma 
---
  .../intel-gpu-tools/intel-gpu-tools_1.11.bb| 24 ++
  .../intel-gpu-tools/intel-gpu-tools_1.9.bb | 19 -
  2 files changed, 24 insertions(+), 19 deletions(-)
  create mode 100644 
common/recipes-graphics/intel-gpu-tools/intel-gpu-tools_1.11.bb
  delete mode 100644 
common/recipes-graphics/intel-gpu-tools/intel-gpu-tools_1.9.bb

diff --git a/common/recipes-graphics/intel-gpu-tools/intel-gpu-tools_1.11.bb 
b/common/recipes-graphics/intel-gpu-tools/intel-gpu-tools_1.11.bb
new file mode 100644
index 000..476508d
--- /dev/null
+++ b/common/recipes-graphics/intel-gpu-tools/intel-gpu-tools_1.11.bb
@@ -0,0 +1,24 @@
+require ${COREBASE}/meta/recipes-graphics/xorg-app/xorg-app-common.inc
+
+SUMMARY = "Intel GPU tools"
+DESCRIPTION = "Variety of small tools for testing intel graphics."
+
+SRC_URI[md5sum] = "836e9fd084f63da2a29fe81a47eb3db8"
+SRC_URI[sha256sum] = 
"48823450452b57c52c74e00c8c763ed7cdd0c81cc877e8c2f619f7f6c45dade4"
+
+LIC_FILES_CHKSUM = "file://COPYING;md5=0918806acfedc3e8c0488f2dd61616dd"
+
+inherit autotools gtk-doc
+
+DEPENDS += "libdrm libpciaccess cairo udev glib-2.0 libxv libx11 libxext 
libxrandr"
+
+PACKAGECONFIG ??= ""
+PACKAGECONFIG[libunwind] = 
"--with-libunwind,--without-libunwind,libunwind,libunwind"
+
+EXTRA_OECONF = "--disable-nouveau --disable-shader-debugger --disable-dumper"
+COMPATIBLE_HOST = "(x86_64.*|i.86.*)-linux"
+
+gputools_sysroot_preprocess() {
+   rm -f ${SYSROOT_DESTDIR}${libdir}/pkgconfig/intel-gen4asm.pc
+}
+SYSROOT_PREPROCESS_FUNCS += "gputools_sysroot_preprocess"
diff --git a/common/recipes-graphics/intel-gpu-tools/intel-gpu-tools_1.9.bb 
b/common/recipes-graphics/intel-gpu-tools/intel-gpu-tools_1.9.bb
deleted file mode 100644
index b98fc75..000
--- a/common/recipes-graphics/intel-gpu-tools/intel-gpu-tools_1.9.bb
+++ /dev/null
@@ -1,19 +0,0 @@
-require ${COREBASE}/meta/recipes-graphics/xorg-app/xorg-app-common.inc
-
-SUMMARY = "Intel GPU tools"
-DESCRIPTION = "Variety of small tools for testing intel graphics."
-
-SRC_URI[md5sum] = "1e768f2b1edc8613911b1d33bb361a7f"
-SRC_URI[sha256sum] = 
"1de4c28ae0fe1e6c198ab559dbffcec6762798dc4adbdfdac54b2c7a9b0a1ed3"
-
-LIC_FILES_CHKSUM = "file://COPYING;md5=0918806acfedc3e8c0488f2dd61616dd"
-
-DEPENDS += "libdrm libpciaccess cairo udev glib-2.0 libxv libx11 libxext 
libxrandr"
-
-EXTRA_OECONF = "--disable-nouveau --disable-shader-debugger --disable-dumper"
-COMPATIBLE_HOST = "(x86_64.*|i.86.*)-linux"
-
-gputools_sysroot_preprocess() {
-   rm -f ${SYSROOT_DESTDIR}${libdir}/pkgconfig/intel-gen4asm.pc
-}
-SYSROOT_PREPROCESS_FUNCS += "gputools_sysroot_preprocess"


--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH V2] intel-gpu-tools: upgrade to version 1.11

2015-08-11 Thread Burton, Ross

On 11 August 2015 at 16:26, Saul Wold  wrote:

> Also, did you do a remove and recreate of the recipe or a "git mv"
> Normally we do a git mv and then can clearly see the difference between the
> 2 versions as git will handle the move easier.
>

As far as git is concerned there is no difference, the nicer patches come
from passing -M to git format-patch which will try and detect a rename.

Ross
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [fido][PATCH 1/1] common/linux-yocto_3.14: update meta branch SRCREV

2015-08-11 Thread Darren Hart



On 8/11/15 12:56 AM, Wu, Chia Chuan wrote:
> 
> 
>> -Original Message-
>> From: Darren Hart [mailto:dvh...@linux.intel.com]
>> Sent: Thursday, August 6, 2015 7:17 AM
>> To: Wu, Chia Chuan 
>> Cc: meta-intel@yoctoproject.org
>> Subject: Re: [meta-intel] [fido][PATCH 1/1] common/linux-yocto_3.14: update
>> meta branch SRCREV
>>
>> On 8/3/15 3:03 AM, chia.chuan...@intel.com wrote:
>>> From: Wu Chia Chuan 
>>>
>>> Enable i40e network driver for Intel Ethernet Controller XL710/X710 on
>>> Intel common BSP so that the NIC card is discoverable under River Forest
>> platform.
>>>
>>
>> This fails to apply to master, and we don't apply patches to fido that 
>> haven't
>> been first applied to master.
>>
>> Please develop against master and request backports to the stable branches.
> Darren, linux-yocto meta branch was separated out in master branch and 
> pointing  
> to " yocto-kernel-cache" repo. Fido branch still use the meta branch from 
> "linux-yocto-3.xx" repo, the revisions would not be common for the two 
> branches.
> 
> This patch is required for River Forest BSP ,which is developed/tested under 
> fido branch.

Right you are. Thanks for pointing that out.

This kind of justification should be included in the commit message for
any patch that cannot be applied to master first as it is a special case.

-- 
Darren Hart
Intel Open Source Technology Center
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [fido][PATCH 1/1] common/linux-yocto_3.14: update meta branch SRCREV

2015-08-11 Thread Wu, Chia Chuan



> -Original Message-
> From: Darren Hart [mailto:dvh...@linux.intel.com]
> Sent: Wednesday, August 12, 2015 12:42 AM
> To: Wu, Chia Chuan 
> Cc: meta-intel@yoctoproject.org
> Subject: Re: [meta-intel] [fido][PATCH 1/1] common/linux-yocto_3.14: update
> meta branch SRCREV
> 
> 
> 
> On 8/11/15 12:56 AM, Wu, Chia Chuan wrote:
> >
> >
> >> -Original Message-
> >> From: Darren Hart [mailto:dvh...@linux.intel.com]
> >> Sent: Thursday, August 6, 2015 7:17 AM
> >> To: Wu, Chia Chuan 
> >> Cc: meta-intel@yoctoproject.org
> >> Subject: Re: [meta-intel] [fido][PATCH 1/1] common/linux-yocto_3.14:
> >> update meta branch SRCREV
> >>
> >> On 8/3/15 3:03 AM, chia.chuan...@intel.com wrote:
> >>> From: Wu Chia Chuan 
> >>>
> >>> Enable i40e network driver for Intel Ethernet Controller XL710/X710
> >>> on Intel common BSP so that the NIC card is discoverable under River
> >>> Forest
> >> platform.
> >>>
> >>
> >> This fails to apply to master, and we don't apply patches to fido
> >> that haven't been first applied to master.
> >>
> >> Please develop against master and request backports to the stable branches.
> > Darren, linux-yocto meta branch was separated out in master branch and
> > pointing to " yocto-kernel-cache" repo. Fido branch still use the meta
> > branch from "linux-yocto-3.xx" repo, the revisions would not be common for
> the two branches.
> >
> > This patch is required for River Forest BSP ,which is developed/tested under
> fido branch.
> 
> Right you are. Thanks for pointing that out.
> 
> This kind of justification should be included in the commit message for any 
> patch
> that cannot be applied to master first as it is a special case.
Darren, sure, I should include this information at the beginning of the cover 
letter
 & commit message. Thanks!
> 
> --
> Darren Hart
> Intel Open Source Technology Center
-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH V2] intel-gpu-tools: upgrade to version 1.11

2015-08-11 Thread Pengyu Ma




On 08/11/2015 11:26 PM, Saul Wold wrote:

On 08/10/2015 10:08 PM, Pengyu Ma wrote:

Disable gtk-doc to fix building error.
Add libunwind package config to fix denpendece.

Changes since v1:
  * Add libunwind package config.


During my testing of this, I saw the following warning:
WARNING: QA Issue: 
/usr/lib/intel-gpu-tools/intel-gpu-tools/tools@underscore@test_intel-gpu-tools 
contained in package intel-gpu-tools requires /bin/bash, but no 
providers found in its RDEPENDS [file-rdeps]


It seems that some script in this package requires bash, is it 
possible to remove the bashism and use the standard "/bin/sh" instead?


I didn't see it in my building project, bash should be default shell in 
my building.

Anyway I will create a patch to replace bash with "/bin/sh"".

Also, did you do a remove and recreate of the recipe or a "git mv" 
Normally we do a git mv and then can clearly see the difference 
between the 2 versions as git will handle the move easier.



Will do it in V3.

Pengyu

Thanks
Sau!


Signed-off-by: Pengyu Ma 
---
  .../intel-gpu-tools/intel-gpu-tools_1.11.bb| 24 
++
  .../intel-gpu-tools/intel-gpu-tools_1.9.bb | 19 
-

  2 files changed, 24 insertions(+), 19 deletions(-)
  create mode 100644 
common/recipes-graphics/intel-gpu-tools/intel-gpu-tools_1.11.bb
  delete mode 100644 
common/recipes-graphics/intel-gpu-tools/intel-gpu-tools_1.9.bb


diff --git 
a/common/recipes-graphics/intel-gpu-tools/intel-gpu-tools_1.11.bb 
b/common/recipes-graphics/intel-gpu-tools/intel-gpu-tools_1.11.bb

new file mode 100644
index 000..476508d
--- /dev/null
+++ b/common/recipes-graphics/intel-gpu-tools/intel-gpu-tools_1.11.bb
@@ -0,0 +1,24 @@
+require ${COREBASE}/meta/recipes-graphics/xorg-app/xorg-app-common.inc
+
+SUMMARY = "Intel GPU tools"
+DESCRIPTION = "Variety of small tools for testing intel graphics."
+
+SRC_URI[md5sum] = "836e9fd084f63da2a29fe81a47eb3db8"
+SRC_URI[sha256sum] = 
"48823450452b57c52c74e00c8c763ed7cdd0c81cc877e8c2f619f7f6c45dade4"

+
+LIC_FILES_CHKSUM = 
"file://COPYING;md5=0918806acfedc3e8c0488f2dd61616dd"

+
+inherit autotools gtk-doc
+
+DEPENDS += "libdrm libpciaccess cairo udev glib-2.0 libxv libx11 
libxext libxrandr"

+
+PACKAGECONFIG ??= ""
+PACKAGECONFIG[libunwind] = 
"--with-libunwind,--without-libunwind,libunwind,libunwind"

+
+EXTRA_OECONF = "--disable-nouveau --disable-shader-debugger 
--disable-dumper"

+COMPATIBLE_HOST = "(x86_64.*|i.86.*)-linux"
+
+gputools_sysroot_preprocess() {
+rm -f ${SYSROOT_DESTDIR}${libdir}/pkgconfig/intel-gen4asm.pc
+}
+SYSROOT_PREPROCESS_FUNCS += "gputools_sysroot_preprocess"
diff --git 
a/common/recipes-graphics/intel-gpu-tools/intel-gpu-tools_1.9.bb 
b/common/recipes-graphics/intel-gpu-tools/intel-gpu-tools_1.9.bb

deleted file mode 100644
index b98fc75..000
--- a/common/recipes-graphics/intel-gpu-tools/intel-gpu-tools_1.9.bb
+++ /dev/null
@@ -1,19 +0,0 @@
-require ${COREBASE}/meta/recipes-graphics/xorg-app/xorg-app-common.inc
-
-SUMMARY = "Intel GPU tools"
-DESCRIPTION = "Variety of small tools for testing intel graphics."
-
-SRC_URI[md5sum] = "1e768f2b1edc8613911b1d33bb361a7f"
-SRC_URI[sha256sum] = 
"1de4c28ae0fe1e6c198ab559dbffcec6762798dc4adbdfdac54b2c7a9b0a1ed3"

-
-LIC_FILES_CHKSUM = 
"file://COPYING;md5=0918806acfedc3e8c0488f2dd61616dd"

-
-DEPENDS += "libdrm libpciaccess cairo udev glib-2.0 libxv libx11 
libxext libxrandr"

-
-EXTRA_OECONF = "--disable-nouveau --disable-shader-debugger 
--disable-dumper"

-COMPATIBLE_HOST = "(x86_64.*|i.86.*)-linux"
-
-gputools_sysroot_preprocess() {
-rm -f ${SYSROOT_DESTDIR}${libdir}/pkgconfig/intel-gen4asm.pc
-}
-SYSROOT_PREPROCESS_FUNCS += "gputools_sysroot_preprocess"



--
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

Re: [meta-intel] [PATCH V2] intel-gpu-tools: upgrade to version 1.11

2015-08-11 Thread Pengyu Ma




On 08/11/2015 11:29 PM, Burton, Ross wrote:


On 11 August 2015 at 16:26, Saul Wold > wrote:


Also, did you do a remove and recreate of the recipe or a "git mv"
Normally we do a git mv and then can clearly see the difference
between the 2 versions as git will handle the move easier.


As far as git is concerned there is no difference, the nicer patches 
come from passing -M to git format-patch which will try and detect a 
rename.



Thanks for reminding this, will do it in V3.
Pengyu

Ross


-- 
___
meta-intel mailing list
meta-intel@yoctoproject.org
https://lists.yoctoproject.org/listinfo/meta-intel

[meta-intel] [PATCH v3] intel-gpu-tools: upgrade to version 1.11

2015-08-11 Thread Pengyu Ma

Disable gtk-doc to fix building error.
Add libunwind package config to fix denpendece.

Changes since v2:
 * Remove bash dependency.

Changes since v1:
 * Add libunwind package config.

Signed-off-by: Pengyu Ma 
---
 ...001-test-script-remove-dependency-on-bash.patch | 146 +
 ...el-gpu-tools_1.9.bb => intel-gpu-tools_1.11.bb} |  12 +-
 2 files changed, 156 insertions(+), 2 deletions(-)
 create mode 100644 
common/recipes-graphics/intel-gpu-tools/intel-gpu-tools/0001-test-script-remove-dependency-on-bash.patch
 rename common/recipes-graphics/intel-gpu-tools/{intel-gpu-tools_1.9.bb => 
intel-gpu-tools_1.11.bb} (62%)

diff --git 
a/common/recipes-graphics/intel-gpu-tools/intel-gpu-tools/0001-test-script-remove-dependency-on-bash.patch
 
b/common/recipes-graphics/intel-gpu-tools/intel-gpu-tools/0001-test-script-remove-dependency-on-bash.patch
new file mode 100644
index 000..e93ab64
--- /dev/null
+++ 
b/common/recipes-graphics/intel-gpu-tools/intel-gpu-tools/0001-test-script-remove-dependency-on-bash.patch
@@ -0,0 +1,146 @@
+From a46007ee1644522775c5e429310e0637946818fd Mon Sep 17 00:00:00 2001
+From: Pengyu Ma 
+Date: Wed, 12 Aug 2015 11:01:36 +0800
+Subject: [PATCH] test/script: remove dependency on bash
+
+use /bin/sh instead.
+
+Signed-off-by: Pengyu Ma 
+---
+ scripts/run-tests.sh| 2 +-
+ scripts/who.sh  | 2 +-
+ tests/check_drm_clients | 2 +-
+ tests/ddx_intel_after_fbdev | 2 +-
+ tests/debugfs_emon_crash| 2 +-
+ tests/drv_debugfs_reader| 2 +-
+ tests/drv_missed_irq_hang   | 2 +-
+ tests/drv_module_reload | 2 +-
+ tests/kms_sysfs_edid_timing | 2 +-
+ tests/sysfs_l3_parity   | 2 +-
+ tests/test_rte_check| 2 +-
+ tests/tools_test| 2 +-
+ 12 files changed, 12 insertions(+), 12 deletions(-)
+
+diff --git a/scripts/run-tests.sh b/scripts/run-tests.sh
+index d72fc05..f269567 100755
+--- a/scripts/run-tests.sh
 b/scripts/run-tests.sh
+@@ -1,4 +1,4 @@
+-#!/bin/bash
++#!/bin/sh
+ #
+ # Copyright © 2014 Intel Corporation
+ #
+diff --git a/scripts/who.sh b/scripts/who.sh
+index b221639..205cdca 100755
+--- a/scripts/who.sh
 b/scripts/who.sh
+@@ -1,4 +1,4 @@
+-#!/bin/bash
++#!/bin/sh
+ #
+ # usage: sudo who.sh
+ #
+diff --git a/tests/check_drm_clients b/tests/check_drm_clients
+index eb12416..fed00cd 100755
+--- a/tests/check_drm_clients
 b/tests/check_drm_clients
+@@ -1,4 +1,4 @@
+-#!/bin/bash
++#!/bin/sh
+ 
+ SOURCE_DIR="$( dirname "${BASH_SOURCE[0]}" )"
+ . $SOURCE_DIR/drm_lib.sh
+diff --git a/tests/ddx_intel_after_fbdev b/tests/ddx_intel_after_fbdev
+index bcd2c29..cc3b7cf 100755
+--- a/tests/ddx_intel_after_fbdev
 b/tests/ddx_intel_after_fbdev
+@@ -1,4 +1,4 @@
+-#!/bin/bash
++#!/bin/sh
+ #
+ # Testcase: Load Intel DDX after fbdev was loaded
+ #
+diff --git a/tests/debugfs_emon_crash b/tests/debugfs_emon_crash
+index 809bfab..2e18963 100755
+--- a/tests/debugfs_emon_crash
 b/tests/debugfs_emon_crash
+@@ -1,4 +1,4 @@
+-#!/bin/bash
++#!/bin/sh
+ #
+ # This check if we can crash the kernel with segmentation-fault
+ # by reading /sys/kernel/debug/dri/0/i915_emon_status too quickly
+diff --git a/tests/drv_debugfs_reader b/tests/drv_debugfs_reader
+index 9e2845e..23e9c32 100755
+--- a/tests/drv_debugfs_reader
 b/tests/drv_debugfs_reader
+@@ -1,4 +1,4 @@
+-#!/bin/bash
++#!/bin/sh
+ 
+ SOURCE_DIR="$( dirname "${BASH_SOURCE[0]}" )"
+ . $SOURCE_DIR/drm_lib.sh
+diff --git a/tests/drv_missed_irq_hang b/tests/drv_missed_irq_hang
+index 6e8cfc2..8285bc0 100755
+--- a/tests/drv_missed_irq_hang
 b/tests/drv_missed_irq_hang
+@@ -1,4 +1,4 @@
+-#!/bin/bash
++#!/bin/sh
+ #
+ # Testcase: Simulate missed breadcrumb interrupts
+ #
+diff --git a/tests/drv_module_reload b/tests/drv_module_reload
+index bb29a64..e0398d0 100755
+--- a/tests/drv_module_reload
 b/tests/drv_module_reload
+@@ -1,4 +1,4 @@
+-#!/bin/bash
++#!/bin/sh
+ #
+ # Testcase: Reload the drm module
+ #
+diff --git a/tests/kms_sysfs_edid_timing b/tests/kms_sysfs_edid_timing
+index ec704f6..e90e374 100755
+--- a/tests/kms_sysfs_edid_timing
 b/tests/kms_sysfs_edid_timing
+@@ -1,4 +1,4 @@
+-#!/bin/bash
++#!/bin/sh
+ #
+ # This check the time we take to read the content of all the possible 
connectors.
+ # Without the edid -ENXIO patch 
(http://permalink.gmane.org/gmane.comp.video.dri.devel/62083),
+diff --git a/tests/sysfs_l3_parity b/tests/sysfs_l3_parity
+index 9bd1724..02f763b 100755
+--- a/tests/sysfs_l3_parity
 b/tests/sysfs_l3_parity
+@@ -1,4 +1,4 @@
+-#!/bin/bash
++#!/bin/sh
+ 
+ SOURCE_DIR="$( dirname "${BASH_SOURCE[0]}" )"
+ . $SOURCE_DIR/drm_lib.sh
+diff --git a/tests/test_rte_check b/tests/test_rte_check
+index eb12416..fed00cd 100755
+--- a/tests/test_rte_check
 b/tests/test_rte_check
+@@ -1,4 +1,4 @@
+-#!/bin/bash
++#!/bin/sh
+ 
+ SOURCE_DIR="$( dirname "${BASH_SOURCE[0]}" )"
+ . $SOURCE_DIR/drm_lib.sh
+diff --git a/tests/tools_test b/tests/tools_test
+index a6178e1..5f2d1dc 100755
+--- a/tests/tools_test
 b/tests/tools_test
+@@ -1,4

Re: [meta-intel] [fido][PATCH 1/1] common/linux-yocto_3.14: update meta branch SRCREV

[meta-intel] [PATCH 2/3] libva: upgrade to 1.6.0 (v2)

[meta-intel] [PATCH 1/3] gstreamer-vaapi: upgrade to 0.6.0 (v2)

[meta-intel] [PATCH 3/3] libva-intel-driver: Upgrade to 1.6.0 (v2)

[meta-intel] [PATCH 0/3] Upgrade gstreamer-vaapi, libva & Intel VA driver

Re: [meta-intel] [PATCH 1/3] gstreamer-vaapi: upgrade to 0.6.0 (v2)

Re: [meta-intel] [PATCH 1/3] gstreamer-vaapi: upgrade to 0.6.0 (v2)

[meta-intel] Do we still need GST_API_VERSION inside gstreamer-vaapi-xxx.bb recipes?

Re: [meta-intel] [PATCH 1/3] gstreamer-vaapi: upgrade to 0.6.0 (v2)

Re: [meta-intel] Do we still need GST_API_VERSION inside gstreamer-vaapi-xxx.bb recipes?

Re: [meta-intel] [PATCH V2] intel-gpu-tools: upgrade to version 1.11

Re: [meta-intel] [PATCH V2] intel-gpu-tools: upgrade to version 1.11

Re: [meta-intel] [fido][PATCH 1/1] common/linux-yocto_3.14: update meta branch SRCREV

Re: [meta-intel] [fido][PATCH 1/1] common/linux-yocto_3.14: update meta branch SRCREV

Re: [meta-intel] [PATCH V2] intel-gpu-tools: upgrade to version 1.11

Re: [meta-intel] [PATCH V2] intel-gpu-tools: upgrade to version 1.11

[meta-intel] [PATCH v3] intel-gpu-tools: upgrade to version 1.11

17 matches

Site Navigation

Mail list logo

Footer information