<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - The big SKQP bug" href="https://bugs.freedesktop.org/show_bug.cgi?id=105301#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - The big SKQP bug" href="https://bugs.freedesktop.org/show_bug.cgi?id=105301">bug 105301</a> from <a class="email" href="mailto:dongseong.hwang@intel.com" title="Dongseong Hwang <dongseong.hwang@intel.com>"> Dongseong Hwang</a> <pre>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. <a href="https://www.khronos.org/registry/EGL/extensions/KHR/EGL_KHR_gl_image.txt">https://www.khronos.org/registry/EGL/extensions/KHR/EGL_KHR_gl_image.txt</a> 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>