<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - The big SKQP bug"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105301#c3">Comment # 3</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 <span class="vcard"><a class="email" href="mailto:dongseong.hwang@intel.com" title="Dongseong Hwang <dongseong.hwang@intel.com>"> <span class="fn">Dongseong Hwang</span></a>
</span></b>
<pre>
Tapani, Aditya, I think SKQP has an unnecessary restriction.
"The 2nd step" is how chromium works with media driver in following code.
<a href="https://cs.chromium.org/chromium/src/media/gpu/vaapi/vaapi_picture_native_pixmap_egl.cc?type=cs&q=VaapiPictureNativePixmapEgl::Allocate&l=72">https://cs.chromium.org/chromium/src/media/gpu/vaapi/vaapi_picture_native_pixmap_egl.cc?type=cs&q=VaapiPictureNativePixmapEgl::Allocate&l=72</a>
* chromium creates regular texture
* chromium exports eglImage from the regular texture using eglCreateImageKHR
with EGL_GL_TEXTURE_2D_KHR as EGL_KHR_gl_image spec allows it.
* chromium export dma_buf from eglImage via EGL_MESA_image_dma_buf_export
* chromium gives the dma_buf to libva as external buffer.
The dma_buf can be bound in "another" egl context, so TEXTURE_EXTERNAL_OES with
the eglImage is legit in my opinion.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>