Re: [Mesa-dev] [PATCH] egl/android: Provide an option for the backend to expose KHR_image

2017-12-08 Thread Emil Velikov
On 8 December 2017 at 10:10, Harish Krupo wrote: > Hi Emil, > > Emil Velikov writes: > >> Hi Harish, >> >> On 7 December 2017 at 13:34, Harish Krupo wrote: >>> From android cts 8.0_r4, a new test case checks if

Re: [Mesa-dev] [PATCH] egl/android: Provide an option for the backend to expose KHR_image

2017-12-08 Thread Daniel Stone
Hi Emil, On 7 December 2017 at 18:45, Emil Velikov wrote: > The KHR_image_pixmap extension lists the following as dependency: > > The EGL implementation must define an EGLNativePixmapType (although it > is not required either to export any EGLConfigs supporting

Re: [Mesa-dev] [PATCH] egl/android: Provide an option for the backend to expose KHR_image

2017-12-08 Thread Emil Velikov
On 8 December 2017 at 05:59, Tapani Pälli wrote: > > > On 12/07/2017 08:45 PM, Emil Velikov wrote: >> >> Hi Harish, >> >> On 7 December 2017 at 13:34, Harish Krupo >> wrote: >>> >>> From android cts 8.0_r4, a new test case checks if all the

Re: [Mesa-dev] [PATCH] egl/android: Provide an option for the backend to expose KHR_image

2017-12-08 Thread Harish Krupo
Hi Emil, Emil Velikov writes: > Hi Harish, > > On 7 December 2017 at 13:34, Harish Krupo wrote: >> From android cts 8.0_r4, a new test case checks if all the required egl >> extensions are exposed. In the current implementation we expose

Re: [Mesa-dev] [PATCH] egl/android: Provide an option for the backend to expose KHR_image

2017-12-07 Thread Tapani Pälli
On 12/07/2017 08:45 PM, Emil Velikov wrote: Hi Harish, On 7 December 2017 at 13:34, Harish Krupo wrote: From android cts 8.0_r4, a new test case checks if all the required egl extensions are exposed. In the current implementation we expose KHR_image if

Re: [Mesa-dev] [PATCH] egl/android: Provide an option for the backend to expose KHR_image

2017-12-07 Thread Emil Velikov
Hi Harish, On 7 December 2017 at 13:34, Harish Krupo wrote: > From android cts 8.0_r4, a new test case checks if all the required egl > extensions are exposed. In the current implementation we expose KHR_image > if KHR_image_base and KHR_image_pixmap are supported but

Re: [Mesa-dev] [PATCH] egl/android: Provide an option for the backend to expose KHR_image

2017-12-07 Thread Eric Engestrom
On Thursday, 2017-12-07 19:04:41 +0530, Harish Krupo wrote: > From android cts 8.0_r4, a new test case checks if all the required egl > extensions are exposed. In the current implementation we expose KHR_image > if KHR_image_base and KHR_image_pixmap are supported but KHR_image spec > does not

Re: [Mesa-dev] [PATCH] egl/android: Provide an option for the backend to expose KHR_image

2017-12-07 Thread Tapani Pälli
Looks good, indeed KHR_image spec does not require KHR_image_pixmap or KHR_image_base. Wayland might also be able to enable this but not sure if makes sense there or not. Reviewed-by: Tapani Pälli On 07.12.2017 15:34, Harish Krupo wrote: From android cts 8.0_r4, a

[Mesa-dev] [PATCH] egl/android: Provide an option for the backend to expose KHR_image

2017-12-07 Thread Harish Krupo
From android cts 8.0_r4, a new test case checks if all the required egl extensions are exposed. In the current implementation we expose KHR_image if KHR_image_base and KHR_image_pixmap are supported but KHR_image spec does not mandate the existence of both the extensions. This patch preserves the