Calling random callbacks on the display's event queue is hostile, as
we may call into client code when it least expects it. Create our own
event queue, one per wsi_wl_display, and use that for the registry.
Signed-off-by: Daniel Stone
Cc: mesa-sta...@lists.freedesktop.org
---
src/vulkan/wsi/wsi_
Hi Lionel,
On 12 May 2017 at 10:52, Lionel Landwerlin
wrote:
> On 05/05/17 17:47, Daniel Stone wrote:
>> @@ -535,7 +555,7 @@ wsi_wl_swapchain_acquire_next_image(struct
>> wsi_swapchain *wsi_chain,
>> {
>> struct wsi_wl_swapchain *chain = (struct wsi_wl_swapchain
>> *)wsi_chain;
>> - in
On 05/05/17 17:47, Daniel Stone wrote:
Calling random callbacks on the display's event queue is hostile, as
we may call into client code when it least expects it. Create our own
event queue, one per wsi_wl_display, and use that for the registry.
Signed-off-by: Daniel Stone
Cc: mesa-sta...@lists
Calling random callbacks on the display's event queue is hostile, as
we may call into client code when it least expects it. Create our own
event queue, one per wsi_wl_display, and use that for the registry.
Signed-off-by: Daniel Stone
Cc: mesa-sta...@lists.freedesktop.org
---
src/vulkan/wsi/wsi_
