<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [i915] Feature request: Add support for fencing for PRIME setups" href="https://bugs.freedesktop.org/show_bug.cgi?id=95472#c44">Comment # 44</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [i915] Feature request: Add support for fencing for PRIME setups" href="https://bugs.freedesktop.org/show_bug.cgi?id=95472">bug 95472</a> from <a class="email" href="mailto:axel.davy@ens.fr" title="Axel Davy <axel.davy@ens.fr>"> Axel Davy</a> <pre>(In reply to Chris Wilson from <a href="show_bug.cgi?id=95472#c43">comment #43</a>) > There's no synchronisation point in dri3 with X: > > diff --git a/src/loader/loader_dri3_helper.c > b/src/loader/loader_dri3_helper.c > index a55719a..6b5736b 100644 > --- a/src/loader/loader_dri3_helper.c > +++ b/src/loader/loader_dri3_helper.c > @@ -1399,6 +1399,7 @@ loader_dri3_get_buffers(__DRIdrawable *driDrawable, > buffers->back = back->image; > } > > + loader_dri3_wait_x(draw); > draw->stamp = stamp; > > return true; > > brings it into line with dri2. I don't see why waitX is required. The call has only an impact when a fake front buffer is used. And when fake front buffer is used, the same buffer is always used and it seems correctly updated when needed. (In reply to Mike Lothian from <a href="show_bug.cgi?id=95472#c42">comment #42</a>) Are you sure the dedicated card was not used for this test ? It looks like the problem is the compositor copies the damaged windows contents before the blitImage calls are executed on the gpu. Could it be a problem with the flushing behaviour in intel_blit_image ?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>