Three recent blog postings on DRI3000

[Keith Packard]

Maarten Lankhorst <maarten.lankhorst at canonical.com> writes:

> One of the things that bug me in dri2 is that I have to use the absolute frame number in the swapbuffers call.
> This breaks when moving a window from 1 screen to another. And for example mesa/src/gallium/auxiliary/vl/vl_winsys_dri.c
> has to deal with converting time to frame number, which breaks if a window is moved to another crtc. Instead of scheduling
> frames with absolute frame number, could a system time like CLOCK_MONOTONIC be used instead, and have the kernel
> drm layer round this to the nearest frame?

Present creates a per-window MSC domain, which moves with the window as
it switches screens automatically, so you should be able to at least
consistently schedule swaps across monitors.

Using CLOCK_MONOTONIC does have a certain appeal though; the trouble
here is that applications would essentially have to phase-lock the
system clock with the video clock to avoid occasional glitches.

-- 
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/20130724/e5b9e719/attachment.pgp>