You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

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.		4 years ago
..
drm	backend: introduce wlr_backend_finish	4 years ago
headless	backend/headless: use common renderer and allocator	4 years ago
libinput	backend: introduce wlr_backend_finish	4 years ago
multi	backend: introduce wlr_backend_finish	4 years ago
noop	backend: introduce wlr_backend_finish	4 years ago
session	backend/session: add wlr_device.events.remove	4 years ago
wayland	backend: stop using renderer to get the buffer type	4 years ago
x11	backend: stop using renderer to get the buffer type	4 years ago
backend.c	backend: automatically create allocator	4 years ago
meson.build	Drop RDP backend	5 years ago