Three recent blog postings on DRI3000

[Keith Packard]

Maarten Lankhorst <maarten.lankhorst at canonical.com> 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...

-- 
keith.packard at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 827 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg-devel/attachments/20130725/e483863b/attachment.pgp>