Maarten Lankhorst <[email protected]> writes: > The presentation part of VDPAU (which may be implemented as overlay) offers > something like this with > the VdpPresentationQueueDisplay call. But in dri2 it fails because the window > can get moved between > 2 crtc's, and suddenly you've queued a flip 1000 seconds in the future > because the other crtc was > on for a shorter amount of time.
In DRI3, each window has it's own 'MSC domain', which is guaranteed to be monotonic, and to increment about once per frame. >. With the fence stuff I'm working on it should be possible to insert > a synchronization barrier in the command stream to a crtc that's not on the > same graphics card, but > that really would require cooperation from the drm layer. I'm not sure how this helps? You still need to either know which crtc a presentation *will* occur on or whatever MSC you provide may be wrong... -- [email protected]
pgpS04rv_SG5F.pgp
Description: PGP signature
_______________________________________________ [email protected]: X.Org development Archives: http://lists.x.org/archives/xorg-devel Info: http://lists.x.org/mailman/listinfo/xorg-devel
