[Bug 103202] Tearing with reverse prime (intel primary, nouveau secondary) - bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 103202] Tearing with reverse prime (intel primary, nouveau secondary)
Date: Wed, 11 Oct 2017 09:06:32 +0000	[thread overview]
Message-ID: <bug-103202-8800-h5LocdgOyr@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103202-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>

[-- Attachment #1.1: Type: text/plain, Size: 1105 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=103202

--- Comment #5 from post+fdo-8yesU2pFZgY@public.gmane.org ---
> if the drivers for both GPUs use the ScreenRec::SyncSharedPixmap hook. You can take a look at xf86-video-amdgpu/ati for an example. (The driver of the displaying GPU also needs to separately prevent tearing of the scanout process itself. xf86-video-amdgpu/ati do this by default for PRIME outputs)

So this would be a matter of patching modesetting to do both of these things? 
(I also wouldn't mind using the intel/nouveau Xorg drivers, but I got the
impression that modesetting is actually preferred, at least for newer Intel
cards.)

That talk btw says that modesetting supports both "PRIME sync output slave" and
"PRIME sync output master", which makes me wonder why it is not able to sync
with itself.  Either there's a bug in that (so I should reassign), or the
underlying DRM lacks some support for something (so this bugreport would be in
the right place).  How could I figure that out?

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1919 bytes --]

[-- Attachment #2: Type: text/plain, Size: 154 bytes --]

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/nouveau