On 22/10/16 07:00 PM, Chris Wilson wrote: > This applies a synchronisation point to GetBuffers() such that binding a > texture-from-pixmap its rendering is serialised with X. This matches the > synchronisation point inside DRI2, but it is also arguable that implied > sync should be explicitly handled by the client by calling glXWaitX() > following the binding of all textures. However, currently glXWaitX() > only operates on the bound drawable and does not actually flush all > Pixmaps associated with the bound context. > > This fixes an issue (output lag) where the compositor calls glXWaitX() > prior to acquiring the damage region from X and binding the > texture-from-pixmap.
The X server / driver is responsible for flushing the GPU rendering corresponding to damage events before they are sent to clients. The modesetting driver is known broken in this regard; are there any other setups where this is not happening? -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/mesa-dev
