https://bugs.kde.org/show_bug.cgi?id=521142
Zamundaaa <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Status|REPORTED |RESOLVED Resolution|--- |INTENTIONAL --- Comment #2 from Zamundaaa <[email protected]> --- The removed copy paths aren't related to direct scanout, they're for compositing and only get used as a fallback if copying with OpenGL fails. > The NVIDIA GPU's rendered frames are being routed through KWin's multi-GPU > copy path. For fully discrete PCIe cards with no shared memory this copy path > is not a viable fallback — it defeats the entire purpose of the render > offload configuration. The driver is doing the copy in the application (no matter what KWin does), KWin just composites on the Intel GPU with the buffer it gets from the app. It's possible that https://invent.kde.org/plasma/kwin/-/commit/413face71a9b4c622c2817b8da5d888e2cd77f38 changed which format happens to be used on your display, and that switching it to the application buffer requires a modeset now where it didn't require one before. That's the only explanation I can think of. But in general, you cannot expect direct scanout between GPUs to work. In situations we can detect it, we even explicitly reject doing that in KWin, since we hit a lot of driver bugs with that in the past. -- You are receiving this mail because: You are watching all bug changes.
