<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - EGL_EXT_image_dma_buf_import too limited on i965"
href="https://bugs.freedesktop.org/show_bug.cgi?id=87452#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - EGL_EXT_image_dma_buf_import too limited on i965"
href="https://bugs.freedesktop.org/show_bug.cgi?id=87452">bug 87452</a>
from <span class="vcard"><a class="email" href="mailto:chad.versace@intel.com" title="Chad Versace <chad.versace@intel.com>"> <span class="fn">Chad Versace</span></a>
</span></b>
<pre>One reason that i965 imposes restrictions on dma_buf-EGLImages is to prevent
bugs due to missing compression resolves and mishandling of image orphaning
rules.
Chrome OS also wants to remove some restrictions. It wants to use the EGLImage
for renderbuffer storage with glEGLImageTargetRenderbufferStorageOES.
I think it's time that we start removing i965's restrictions, but do so
carefully without introducing subtle bugs. To allow
glEGLImageTargetRenderbufferStorageOES with dma_buf-EGLImages, all I think is
needed is that i965 disable allocation of auxillary compression buffers (MCS
and HiZ) for such renderbuffers. To allow glEGLImageTargetTexture2DOES,
auxillary surfaces must be disabled as for renderbuffers. More safeguards are
probably needed for textures to implement orphaning rules, but I can't think of
them off the cuff.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>