On Tue, 1 Apr 2003, Sven Luther wrote:
> On Mon, Mar 31, 2003 at 03:34:43PM -0500, Mark Vojkovich wrote:
> >
> > I stripped forum from the reply since devel is more appropriate.
>
> Ok, no problem with me.
>
> > The reason why this doesn't work reliably in the "nv" driver is
> > because there is not an I2C bus - there are THREE of them - and it's
> > not clear which one the driver should be looking on. They're not
>
> One for each head ans one for the video port ?
One for each head and another for other stuff, which can instead
be on the first two in some cases.
>
> > even the same between one card and the next since different board
> > vendors can lay the cards out differently. If I know the correct
> > bus, detection of the flat panel is trivial.
>
> This is a problem because you don't have full documentation, isn't it ?
I have all the hardware documentation that I need, there's just
too much variation in the board layouts to make assumptions about
how things are laid out. I need to actually look for flat panels
on all busses. The code to look for a panel on a bus is in the
core server, but I'm not yet familiar with how to get it to run
on multiple busses.
>
> > I am looking into this problem, but I'm not familiar with
> > XFree86's DDC code, and haven't found someone who is.
>
> This is probably because nobody really is, and because the DDC code is
> not really used right now. The standard open source reply is : "you are
> interested in this ? you just have become the official expert on it." :)
Yes, I'm aware of that. However, I am not yet an expert on it,
so the problem is not yet solved.
> Currently, at least for the glint driver, the DDC/I2C info is read at
> ModeInit time, which is too late to do anything apart print the result
> of the edid read.
The "nv" driver also does things a little to late to be useful.
Mark.
_______________________________________________
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
