Re: [Mesa-dev] [PATCH] glx/dri3: Use four buffers until X driver supports async flips

2014-09-29 Thread Jason Ekstrand
I can't really verify the X bits of this patch. However, I do understand the problem and I can verify that using quad-buffering is a totally sane solution. We had this issue about a year ago with Wayland apps trying to do eglSwapInterval(0) and mesa quad-buffers in that case too. Acked-by:

Re: [Mesa-dev] [PATCH] glx/dri3: Use four buffers until X driver supports async flips

2014-09-29 Thread Dylan Baker
Tested-by: Dylan Baker baker.dyla...@gmail.com On Wednesday, July 02, 2014 02:28:07 PM Keith Packard wrote: A driver which doesn't have async flip support will queue up flips without any way to replace them afterwards. This means we've got a scanout buffer pinned as soon as we schedule a flip

Re: [Mesa-dev] [PATCH] glx/dri3: Use four buffers until X driver supports async flips

2014-09-29 Thread Matt Turner
Cc'ing people who might be able to review. ___ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [PATCH] glx/dri3: Use four buffers until X driver supports async flips

2014-07-02 Thread Keith Packard
A driver which doesn't have async flip support will queue up flips without any way to replace them afterwards. This means we've got a scanout buffer pinned as soon as we schedule a flip and so we need another buffer to keep from stalling. When vblank_mode=0, if there are only three buffers we do: