[Libva] [LIBVA_INTEL_DRIVER][PATCH 1/3] Move some VPP structures/functions into the common files to support more platforms

This is to define some common structures/functions so that they can be used on more platforms when adding new VPP functions. Signed-off-by: Zhao Yakui --- src/Makefile.am | 2 ++ src/gen75_picture_process.c | 1 + src/gen8_post_processing.h | 8 - src/gen9_post_pr

[Libva] [LIBVA_INTEL_DRIVER][PATCH 2/3] Rewrite Media_kernel to optimize the YUV420 8Bit-scaling on Gen9+

The following conversion is supported: NV12->NV12 NV12->I420 I420->NV12 I420->I420 Signed-off-by: Zhao Yakui --- src/Makefile.am| 1 + src/gen75_picture_process.c| 34 +++ src/gen8_post_processing.c | 5 + src/gen9_post

[Libva] [LIBVA_INTEL_DRIVER][PATCH 3/3] Rewrite Media_kernel to optimize the YUV420 8Bit-scaling on Gen8

The following conversion is supported: NV12->NV12 NV12->I420 I420->NV12 I420->I420 Signed-off-by: Zhao Yakui --- src/gen8_post_processing.c | 450 + src/intel_common_vpp_internal.c| 10 +- src/intel_common_vpp_internal.h

Re: [Libva] [PATCH v2] va.h: fix compile warning

Applied. Thanks Haihao > If we specify compiling option with "-Werror=strict-prototypes", we > will get the following error: > va/va.h:294:1: error: function declaration isn't a prototype [- > Werror=strict-prototypes] > typedef int (*VAPrivFunc)(); > > This patch declares the VAPrivFunc with p

Re: [Libva] [PATCH][libva-intel-driver] i965_GetDisplayAttributes: propagate flags from src to dst

LGTM, applied. Thanks Haihao > flags need to be propagated for user to know which flags > are supported by VADisplayAttribType. > > When only VA_DISPLAY_ATTRIB_SETTABLE is reported as flag > then it has to be propagated back to user.  The rest of the > values should be left untouched > > Sign

[Libva] [PATCH v2] va.h: fix compile warning

If we specify compiling option with "-Werror=strict-prototypes", we will get the following error: va/va.h:294:1: error: function declaration isn't a prototype [-Werror=strict-prototypes] typedef int (*VAPrivFunc)(); This patch declares the VAPrivFunc with parameter 'void', to make the compiler ha

Re: [Libva] [PATCH intel-driver 0/5] JPEG Encode Test Speed Optimization

Hi Sean, The configuration is very simple and I ran the test within a text console. Maybe it is a random issue so it is hard to reproduce in your side. I will try to debug it.  Thanks Haihao > Hello Haihao, > > If you like, please file a bug and provide details about your system > configurati

Re: [Libva] [PATCH] va.h: fix compile warning

I also see the same error with '-Werror=strict-prototypes'.  It might causes a compatibility issue if user writes similar code below:   VAPrivFunc foo = vaGetLibFunc(va_dpy, "va_priv_foo");   if (foo) foo("testing"); error info: 161:7: error: too many arguments to function ‘foo’   

Re: [Libva] [PATCH] va.h: fix compile warning

> On 21 November 2016 at 15:25, Xiang, Haihao > wrote: > > Although taking unspecified arguments is obsolete, I don't see any > > failure caused by ' typedef int (*VAPrivFunc)()' > > Which compiler are you using, could you provide more info in the > > commit log? > > > Add "-pedantic" and you'll

Re: [Libva] [PATCH] va.h: fix compile warning

On 11/22/2016 08:51 AM, Li, ZhijianX wrote: -Original Message- From: Xiang, Haihao Sent: Monday, November 21, 2016 11:25 PM To: Li, ZhijianX; libva@lists.freedesktop.org Subject: RE: [Libva] [PATCH] va.h: fix compile warning Although taking unspecified arguments is obsolete, I don't s

Re: [Libva] [PATCH] va.h: fix compile warning

> -Original Message- > From: Xiang, Haihao > Sent: Monday, November 21, 2016 11:25 PM > To: Li, ZhijianX ; libva@lists.freedesktop.org > Subject: RE: [Libva] [PATCH] va.h: fix compile warning > > Although taking unspecified arguments is obsolete, I don't see any failure > caused by ' typ

[Libva] [PATCH][libva-intel-driver] i965_GetDisplayAttributes: propagate flags from src to dst

flags need to be propagated for user to know which flags are supported by VADisplayAttribType. When only VA_DISPLAY_ATTRIB_SETTABLE is reported as flag then it has to be propagated back to user. The rest of the values should be left untouched Signed-off-by: Daniel Charles --- src/i965_drv_vide

Re: [Libva] [PATCH intel-driver 0/5] JPEG Encode Test Speed Optimization

Hello Haihao, If you like, please file a bug and provide details about your system configuration and the errors you are seeing. I'm not able to duplicate your errors. Sean On Sun, Nov 20, 2016 at 7:18 PM, Xiang, Haihao wrote: > > I ran gtest again and got 2 failed cases now: > > [==]

Re: [Libva] [PATCH] va.h: fix compile warning

On 21 November 2016 at 15:25, Xiang, Haihao wrote: > Although taking unspecified arguments is obsolete, I don't see any failure > caused by ' typedef int (*VAPrivFunc)()' > Which compiler are you using, could you provide more info in the commit log? > Add "-pedantic" and you'll see a warning on p

Re: [Libva] [PATCH] va.h: fix compile warning

Although taking unspecified arguments is obsolete, I don't see any failure caused by ' typedef int (*VAPrivFunc)()' Which compiler are you using, could you provide more info in the commit log? Thanks Haihao >-Original Message- >From: Libva [mailto:libva-boun...@lists.freedesktop.org] On

Re: [Libva] [LIBVA_INTEL_DRIVER][PATCH V3 1/4] Query the kernel API to check the EU counts of GPU device

Thanks for the patched, pushed to git. >-Original Message- >From: Libva [mailto:libva-boun...@lists.freedesktop.org] On Behalf Of Zhao >Yakui >Sent: Monday, November 21, 2016 3:42 AM >To: libva@lists.freedesktop.org >Subject: [Libva] [LIBVA_INTEL_DRIVER][PATCH V3 1/4] Query the kernel API

[Libva] [PATCH] va.h: fix compile warning

define the VAPrivFunc with parameter 'void' va.h will be installed, and it will cause a compiling failure if someone include this header to his code. So this change make the compiler happy. Signed-off-by: Li Zhijian --- va/va.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a