RandR version 1.2 revisited

[Keith Packard]

On Wed, 2006-09-13 at 20:14 +0200, Xavier Bestel wrote:

> The problem is in selecting which vblank to sync to. AFAICS the only way
> is for the app to look at RandR's map of the CRTCs, deduce which one
> matches the most with its own window coordinates, and then ask to be
> synchronized with this one. The trouble is in correlating Sync's and
> RandR's Output id.

Right, sync will need to advertise clocks related to each CRTC rather
than only to each screen. Fortunately, it's reasonably easy to add new
sync objects. It needs fixing, but it's not part of the RandR
specification.

> That would have helped for the gamma setting: the "gamma setter" could
> choose a particular output to drive, and then change gamma/whatever. No
> need to touch the one-head-only parts of the protocol.
> I admit it's a bit circonvoluted.

Like I said, we can, by convention, just use the first OUTUPT in the
CRTC's list as the 'special' OUTPUT. 

-- 
keith.packard at intel.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.x.org/archives/xorg/attachments/20060913/898991bc/attachment.pgp>