[Bug 105301] The big SKQP bug

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=105301

--- Comment #2 from Aditya Swarup <aditya.swarup at intel.com> ---
After going through the specs for OES_EGL_image_external  and external textures
in OpenGL spec, my understanding is that there are no limitations/restriction
or special conditions to binding existing texture object to External texture.
Only limitation from the spec is that "If the new texture object is bound to
TEXTURE_2D, TEXTURE_CUBE_MAP, or TEXTURE_EXTERNAL_OES it is and remains a 2-D,
cube map or external texture respectively until it is deleted".

Another point I would like to add is - In the specs it is not mentioned that
EGLImages should only be created with EGL_EXT_image_dma_buf_import. I think
we(Intel) are imposing the restriction that EGL image will only be supported
through Linux dma buf by using extension EGL_LINUX_DMA_BUF_EXT.

Also, this test passes on ARM(Pixel 2 phones) and seems to be only affecting
Intel platforms.

I understand that 2D textures are different from external textures.

>From the specs it seems to be wrt usage of following operations TexImage2D,
TexSubImage2D,CompressedTexImage2D, CompressedTexSubImage2D, CopyTexImage2D, or
CopyTexSubImage2D not permitted for external textures(which should be an
INVALID operation for external textures in any case and since the texture
object is bound to TEXTURE_EXTERNAL_OES, it shouldn't matter if EGLImage
resource was created with a regular texture. It would be considered an external
texture till it is deleted).

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-3d-bugs/attachments/20181011/1a77af06/attachment.html>