RandR 1.3 additions?

[Matthias Hopf]

On Jul 16, 07 12:44:44 -0700, Keith Packard wrote:
> > In order to have this information in a backwards-compatible form
> > (without having to change the protocol), I suggest adding *mandatory*
> > output properties with V1.3. At least the specification of the type of
> > connector should be mandatory. Then tools like xrandr can easily set a
> > mode e.g. to an internal monitor only.
> That sounds like a very reasonable idea. I thought briefly of using
> standardized output names, but realized that we'd quickly end up in the
> XLFD horror where we try to pack a bunch of information into a string.
> If you could put together some list of such properties along with their
> standard values, I can build suitable infrastructure in the driver stack
> to implement them.

This is what I came up so far. There are a few TODOs in it (though they
can be kicked out immediately w/o changing the context), and I'm a bit
unsure about the EDID property, I just read the header file, not the
real implementation.

It also only lists the signal and connector types I could think of, I'm
pretty sure I missed some. So please brainstorm and add additional ones
if necessary.

This is late, and I don't have any code yet, though it should be pretty
trivial to implement an early version with only the mandatory property.
If this is to late for 1.3, it's certainly something for 1.4.

CU all

Matthias

-- 
Matthias Hopf <mhopf at suse.de>      __        __   __
Maxfeldstr. 5 / 90409 Nuernberg   (_   | |  (_   |__          mat at mshopf.de
Phone +49-911-74053-715           __)  |_|  __)  |__  R & D   www.mshopf.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: randrproto_signal.diff
Type: text/x-patch
Size: 5202 bytes
Desc: not available
URL: <http://lists.x.org/archives/xorg/attachments/20070804/137ca61b/attachment.bin>