<div dir="ltr"><div>AFAIK this was the pre-framebuffer-object / OES_surfaceless_context way of making a context current without (really) having a bound surface. That said I don't think Mesa actually implements that feature correctly, atm I think you'll get a BadValue from the xcb_create_pixmap call, but patches to fix that would be welcome.</div><div><br></div><div>- ajax<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Mon, Jul 18, 2022 at 10:28 PM Lin, Shuicheng <<a href="mailto:shuicheng.lin@intel.com">shuicheng.lin@intel.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div style="overflow-wrap: break-word;" lang="EN-US">
<div class="gmail-m_2423099639048306266WordSection1">
<p class="MsoNormal">Hi,<u></u><u></u></p>
<p class="MsoNormal">In spec, eglCreatePbufferSurface is allowed to be called with attrib_list is NULL or empty, which means EGL_WIDTH/EGL_HEIGHT for the surface is 0.<u></u><u></u></p>
<p class="MsoNormal">And in mesa code, specific to android path, I cannot find the width/height could be updated to a normal value.<u></u><u></u></p>
<p class="MsoNormal">Also the eglMakeCurrent call after the eglCreatePbufferSurface, will use the 0 width/height to allocate buffer, which seems un-reasonable.<u></u><u></u></p>
<p class="MsoNormal">Could you share me why 0 is allowed for width/height, and how app will use the PbufferSurface later?<u></u><u></u></p>
<p class="MsoNormal">Thanks.<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
<p class="MsoNormal">Best Regards<u></u><u></u></p>
<p class="MsoNormal">Shuicheng<u></u><u></u></p>
<p class="MsoNormal"><u></u> <u></u></p>
</div>
</div>
</blockquote></div>