[Bug 105301] The big SKQP bug

[bugzilla-daemon at freedesktop.org]

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

--- Comment #4 from Dongseong Hwang <dongseong.hwang at intel.com> ---
Correction: in Chromium case above, it uses GL_TEXTURE_2D.

The source of all confusion is EGL_KHR_gl_image spec, which allows to create
eglImage from regular texture.
https://www.khronos.org/registry/EGL/extensions/KHR/EGL_KHR_gl_image.txt

Unfortunately, the spec doesn't define which texture <target> parameter we must
use for EGLImageTargetTexture2DOES API.

ARM driver allows TEXTURE_BINDING_EXTERNAL_OES but Mesa allows only TEXTURE_2D
in this case.

in EGL_KHR_gl_image case, we create eglImage by eglCreateImageKHR with
EGL_GL_TEXTURE_2D_KHR <target> parameter, but the spec doesn't explicitly say
which TEXTURE_BINDING_EXTERNAL_OES or TEXTURE_2D must be used for
EGLImageTargetTexture2DOES.

Worth to note, EGL_EXT_image_dma_buf_import spec also doesn't explicitly say
which TEXTURE_BINDING_EXTERNAL_OES or TEXTURE_2D must be used for
EGLImageTargetTexture2DOES. in this case, we create eglImage by
eglCreateImageKHR with EGL_LINUX_DMA_BUF_EXT <target> parameter, and use
TEXTURE_BINDING_EXTERNAL_OES for EGLImageTargetTexture2DOES without any spec
support.

It's really gray area. I'm not sure which skia or mesa we should change.

-- 
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/20181016/e1b0e200/attachment.html>