Simon Ser ce3e819b33 backend: stop using renderer to get the buffer type ... When picking a format, the backend needs to know whether the buffers allocated by the allocator will be DMA-BUFs or shared memory. So far, the backend used the renderer's supported buffer types to guess this information. This is pretty fragile: renderers in general don't care about the SHM cap (they only care about the DATA_PTR one). Additionally, nothing stops a renderer from supporting both DMA-BUFs and shared memory, but this would break the backend's guess. Instead, use wlr_allocator.buffer_caps. This is more reliable since the buffers created with the allocator are guaranteed to have these caps.		2021-05-31 15:50:13 -04:00
..
drm	backend: introduce wlr_backend_finish	2021-05-21 22:13:54 +02:00
headless	backend/headless: use common renderer and allocator	2021-05-21 22:13:54 +02:00
libinput	backend: introduce wlr_backend_finish	2021-05-21 22:13:54 +02:00
multi	backend: introduce wlr_backend_finish	2021-05-21 22:13:54 +02:00
noop	backend: introduce wlr_backend_finish	2021-05-21 22:13:54 +02:00
session	backend/session: add wlr_device.events.remove	2021-04-27 09:11:44 +02:00
wayland	backend: stop using renderer to get the buffer type	2021-05-31 15:50:13 -04:00
x11	backend: stop using renderer to get the buffer type	2021-05-31 15:50:13 -04:00
backend.c	backend: automatically create allocator	2021-05-21 22:13:54 +02:00
meson.build	Drop RDP backend	2020-01-10 19:38:39 +01:00