diff options
author | Simon Ser <contact@emersion.fr> | 2021-05-31 21:02:31 +0200 |
---|---|---|
committer | Simon Zeni <simon@bl4ckb0ne.ca> | 2021-05-31 15:50:13 -0400 |
commit | ce3e819b33c47974e0d635e87381800ac3c8df59 (patch) | |
tree | 96720e0bfbe2690395337a3d4d8b14fb47055640 /render | |
parent | 766a24fa7791d115fa36aded57d7cde87b20d4da (diff) |
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.
Diffstat (limited to 'render')
0 files changed, 0 insertions, 0 deletions