So, it's a TVOUT, but it has one major difference... it's a second head that has its own refresh and modeline setup. I wasn't aware that this was what was going on. With that setup, if there's no scaling going on in the tvout part of the chip, it's possible generate a (relatively) exact modeline that's NTSC-correct. It sounds like through the DirectFB framework that's possible, from what you say.It plugs into the 2nd head 15pin standard vga connector on the card and has svideo and composite on the other end. That is for a G400 standard (in the bedroom computer) and the other option is for the G400 with the MJPEG junk in it and that is a whole break-out box with composite, s-video and audio connectors on it.
All the rants before were assuming a "normal" tvout setup. A VGA monitor plugged in, and a tvout chip (or part of the GPU) redoing the scaling. In both cases, I stand by the decoding genlock thing... where the decoding of video fields needs to by synchronised to the hardware refresh.
The NVidia driver sometimes puts constraints on the modeline numbers to do hardware issues that made someone's silicon math easier. "Not a multiple of 8" and things like that. That might be the sort of thing you're running into there.If you melt your stuff, you've been warned!
:-)
Didn't work unfortunately. I got an error in the console log from the matroxfb driver that it could not set 720 so used 736 instead.
-Cory
************************************************************************* * Cory Papenfuss * * Electrical Engineering candidate Ph.D. graduate student * * Virginia Polytechnic Institute and State University * *************************************************************************
_______________________________________________ mythtv-users mailing list [email protected] http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-users
