mirror of
https://gitlab.freedesktop.org/pipewire/pipewire.git
synced 2026-02-05 04:06:37 -05:00
58b958860e
A DMA buffer from a DRM device are typically accessed using API related to a DRM device, e.g. Vulkan or EGL. To create such a context for using with a PipeWire stream that passed DRM device DMA buffers applications have so far usually guessed or made use of the same context as the stream content will be presented. This has mostly been the Wayland EGL/Vulkan context, and while this has most of the time worked, it's somewhat by accident, and for reliable operation, PipeWire must be aware of what DRM device a DMA buffer should be accessed using. To address this, introduce device ID negotation, allowing sources and sinks to negotiate what DRM device is supported, and what formats and modifiers are supported by them. This will allow applications to stop relying on luck or the windowing system to figure out how to access the DMA buffers. It also paves the way for being able to use multiple GPUs for different video streams, depending on what the sources and sinks support. |
||
|---|---|---|
| .. | ||
| examples | ||
| include | ||
| include-private/spa-private | ||
| lib | ||
| plugins | ||
| tests | ||
| tools | ||
| meson.build | ||