commit | e1e05afec7d7d10bb77fd00c5bd72cf17d77120d | [log] [tgz] |
---|---|---|
author | Jan Grulich <grulja@gmail.com> | Tue Sep 21 18:36:16 2021 |
committer | WebRTC LUCI CQ <webrtc-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Oct 06 10:31:51 2021 |
tree | 08bbc7c34c44020fad2db564dccb14170fdcd37a | |
parent | 404cd60ecce1879ce1c9c593ca0d0cb9784e0589 [diff] |
Reland "PipeWire capturer: implement proper DMA-BUFs support"" This is a reland of f2177f6612079ccce9c320ea7e77bc934c684f5c Original change's description: > PipeWire capturer: implement proper DMA-BUFs support > > Currently both KWin (KDE) and Mutter (GNOME) window managers don't > use DMA-BUFs by default, but only when client asks specifically for > them (KWin) or when experimental DMA-BUF support is enabled (Mutter). > While current implementation works just fine on integrated graphics > cards, it causes issues on dedicated GPUs (AMD and NVidia) where the > code either crashes or screensharing is slow and unusable. > > To fix this, DMA-BUFs has to be opened using OpenGL context and not > being directly mmaped(). This implementation requires to use DMA-BUF > modifiers, as they are now mandatory for DMA-BUFs usage. > > Documentation for this behavior can be found here: > https://gitlab.freedesktop.org/pipewire/pipewire/-/blob/master/doc/dma-buf.dox > > Bug: chromium:1233417 > Change-Id: I0cecf16d6bb0f576954b9e8f071cab526f7baf2c > Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/227022 > Commit-Queue: Tommi <tommi@webrtc.org> > Reviewed-by: Tommi <tommi@webrtc.org> > Reviewed-by: Erik Språng <sprang@webrtc.org> > Cr-Commit-Position: refs/heads/main@{#34889} Bug: chromium:1233417 Change-Id: I308501d86ec18ab6df9bcee569c4b72df7926549 Reviewed-on: https://webrtc-review.googlesource.com/c/src/+/231180 Reviewed-by: Erik Språng <sprang@webrtc.org> Reviewed-by: Tommi <tommi@webrtc.org> Commit-Queue: Tommi <tommi@webrtc.org> Cr-Commit-Position: refs/heads/main@{#35152}
WebRTC is a free, open software project that provides browsers and mobile applications with Real-Time Communications (RTC) capabilities via simple APIs. The WebRTC components have been optimized to best serve this purpose.
Our mission: To enable rich, high-quality RTC applications to be developed for the browser, mobile platforms, and IoT devices, and allow them all to communicate via a common set of protocols.
The WebRTC initiative is a project supported by Google, Mozilla and Opera, amongst others.
See here for instructions on how to get started developing with the native code.
Authoritative list of directories that contain the native API header files.