Hans de Goede <hdego...@redhat.com> writes: > When using reverse prime we do 2 copies, 1 from the primary GPU's > framebuffer to a shared pixmap and 1 from the shared pixmap to the > secondary GPU's framebuffer. > > This means that on the primary GPU side the copy MUST be finished, > before we start the second copy (before the secondary GPU's driver > starts processing the damage on the shared pixmap). > > This fixes secondary outputs sometimes showning (some) old fb contents, > because of the 2 copies racing with each other, for an example of > what this looks like see:
Is working around the fact that the primary and secondary aren't cooperating on dmabuf fencing? Should they be doing that instead? Or would glamor_flush be sufficient?
signature.asc
Description: PGP signature
_______________________________________________ xorg-devel@lists.x.org: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: https://lists.x.org/mailman/listinfo/xorg-devel
