Re: [Mesa-dev] [PATCH] egl/wayland: Ensure we get a back buffer

2017-05-18 Thread Daniel Stone
Hi Emil, On 18 May 2017 at 17:22, Emil Velikov wrote: > On 16 May 2017 at 11:02, Daniel Stone wrote: >> Ideally get_back_bo() failing should store a failure flag inside the >> surface and cause the next SwapBuffers to fail, but for the meantime,

Re: [Mesa-dev] [PATCH] egl/wayland: Ensure we get a back buffer

2017-05-18 Thread Emil Velikov
Hi Dan, On 16 May 2017 at 11:02, Daniel Stone wrote: > Ideally get_back_bo() failing should store a failure flag inside the > surface and cause the next SwapBuffers to fail, but for the meantime, > restore the correct behaviour such that get_back_bo() no longer fails.

Re: [Mesa-dev] [PATCH] egl/wayland: Ensure we get a back buffer

2017-05-16 Thread Daniel Stone
Hi Pekka, On 16 May 2017 at 11:32, Pekka Paalanen wrote: > On Tue, 16 May 2017 11:02:22 +0100 > Daniel Stone wrote: >> This removed a guarantee that we would've processed all events inside >> get_back_bo(), and introduced a failure whereby the server

Re: [Mesa-dev] [PATCH] egl/wayland: Ensure we get a back buffer

2017-05-16 Thread Pekka Paalanen
On Tue, 16 May 2017 11:02:22 +0100 Daniel Stone wrote: > Commit 9ca6711faa03 changed the Wayland winsys to only block for the > frame callback inside SwapBuffers, rather than get_back_bo. get_back_bo > would perform a single non-blocking Wayland event dispatch, to try to >

[Mesa-dev] [PATCH] egl/wayland: Ensure we get a back buffer

2017-05-16 Thread Daniel Stone
Commit 9ca6711faa03 changed the Wayland winsys to only block for the frame callback inside SwapBuffers, rather than get_back_bo. get_back_bo would perform a single non-blocking Wayland event dispatch, to try to find any release events which we had pulled off the wire but not actually processed.