[randr-1.3] ramdac awareness

Maarten Maathuis madman2003 at gmail.com
Fri Nov 23 01:41:51 PST 2007

But there are outputs which can run on more than one ramdac and those
that can't, so static approaches are out of the question.

You actually need to occupy ramdac 0, even if the "normal" output on
there isn't used. The usual situation is like this:

2 ramdac's, 2 outputs, one can run on the primary ramdac's, the second
can run on both ramdac's.


Maarten Maathuis.

On 11/23/07, Dave Airlie <airlied at gmail.com> wrote:
> On Nov 23, 2007 9:08 AM, Maarten Maathuis <madman2003 at gmail.com> wrote:
> > I can be short about this, the current infrastructure is only crtc
> > aware, this is not enough, since there can be 3 ramdac's and 2 crtc's
> > (for nvidia hardware) and restrictions on who gets what. So a property
> > similar to what crtc's have (a crtc_mask) would be greatly
> > appreciated. Currently i'm working around this, but this has
> > limitations.
> >
> RAMDACs should be == outputs... I think nvidia maybe blurred the lines
> a bit with their naming, but the card does have distinct scan out and
> ouputs ..
> just has really wierd routing behaviour....
> Dave.

More information about the xorg mailing list