weston/libweston/renderer-vulkan
Erico Nunes 1a68480421 backend-drm: use dmabuf renderbuffer for Vulkan
The initial drm backend implementation for Vulkan passes display device
allocated gbm bos directly to the renderer. This is a bit awkward since
it requires the renderer to maintain a custom output creation interface
and another code path for importing specifically gbm bos.
Since then, vulkan-renderer received support to use dmabuf renderbuffers
to support e.g. pipewire dmabuf, in an interface which is also common
with gl-renderer.
The dmabuf renderbuffer code path is similar to what the drm backend
implementation intended to do, so we can unify it to a single interface.
This has the advantages of requiring one less custom output creation
interface, as well as the renderer being able to handle the drm backend
through a single shared dmabuf renderbuffer path.

Signed-off-by: Erico Nunes <nunes.erico@gmail.com>
2025-09-12 18:04:57 +01:00
..
meson.build libweston: Vulkan renderer 2025-05-23 20:36:05 +01:00
vulkan-pipeline.c libweston: Vulkan renderer 2025-05-23 20:36:05 +01:00
vulkan-pixel-format.c vulkan-renderer: Add query to populate shm formats 2025-09-08 12:02:11 +01:00
vulkan-renderer-internal.h vulkan-renderer: Add query to populate shm formats 2025-09-08 12:02:11 +01:00
vulkan-renderer.c backend-drm: use dmabuf renderbuffer for Vulkan 2025-09-12 18:04:57 +01:00
vulkan-renderer.h backend-drm: use dmabuf renderbuffer for Vulkan 2025-09-12 18:04:57 +01:00
vulkan_fragment_shader.frag libweston: Vulkan renderer 2025-05-23 20:36:05 +01:00
vulkan_vertex_shader_surface.vert libweston: Vulkan renderer 2025-05-23 20:36:05 +01:00
vulkan_vertex_shader_texcoord.vert libweston: Vulkan renderer 2025-05-23 20:36:05 +01:00