<html>
<head>
<base href="https://bugs.freedesktop.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [Dri3 bisected] piglit glx_GLX_ARB_create_context_current_with_no_framebuffer fail"
href="https://bugs.freedesktop.org/show_bug.cgi?id=79629#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [Dri3 bisected] piglit glx_GLX_ARB_create_context_current_with_no_framebuffer fail"
href="https://bugs.freedesktop.org/show_bug.cgi?id=79629">bug 79629</a>
from <span class="vcard"><a class="email" href="mailto:xunx.fang@intel.com" title="fangxun <xunx.fang@intel.com>"> <span class="fn">fangxun</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=79629#c7">comment #7</a>)
<span class="quote">> DRI3 is still being developed/stabilized and its interaction with fences
> poorly specified. Mesa does not yet utilize the explicit fences implied in
> the spec.
>
> Chris will disable DRI3 by default in the ddx because there are a number of
> trivial-to-hit bugs that cause X or the compositor to stop updating.
>
> You should cross-reference
> <a class="bz_bug_link
bz_status_NEW "
title="NEW --- - [dri3] Mesa does not support explicit fencing"
href="show_bug.cgi?id=81551">https://bugs.freedesktop.org/show_bug.cgi?id=81551</a> for the patch that will
> identify the issue as being the explicit-vs-implicit fencing issue or
> something new.</span >
It still fails on haswell, broadwell and baytrail with the patch.
NOTE: It passes on ivybridge on latest driver now.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>