On Wed, Mar 05, 2014 at 12:40:34AM -0500, Ilia Mirkin wrote: > On Mon, Mar 3, 2014 at 5:41 PM, Nils Krafft <[email protected]> wrote: > > I have here a GeForce 2MX (NV10) with a Brooktree BT869 chip for the > > TV-Out.
You can try nvtv (http://sourceforge.net/projects/nv-tv-out/). It bypasses X and modesetting and programs the Brooktree and CRTC directly. I've no idea if it still work with modern X and/or nouveau. :-) > > shows me only the DVI connection (in fact it's VGA, not DVI), but not > > the S-Video connection. If not supported, is this planned for future > > versions? > The relevant hardware is not easily available, nor is hardware to > consume s-video/composite connections. I still have some hardware for both, though I haven't used it for a long time. > This sort of thing is probably > only going to be supported if you make it happen. If you're > interested, the relevant source file is > drivers/gpu/drm/nouveau/dispnv04/tvnv04.c, and you'd have to add > something in drivers/gpu/drm/i2c. BT* chips are usually easy to find > docs for, and some of the additional details can probably be worked > out from mmiotraces, assuming you can find a kernel that the blob > driver will load on. It's much better to work from the datasheet instead of doing mmiotraces, the blob only has a few modes built-in. The BT is actually a very flexible chip, and supports a very wide range of modes with different overscan amount, plus different filtering options. It probably wouldn't be hard to just take a few modes from nvtv and put them into nouveau, similar to the (very few) Chrontel modes. What's missing is some sort of infrastructure in X to say "look, on this hardware there are these two functional blocks (CRTC + BT), I would like to program with the following values, and I've specified the values in the config file, or I'm a user space program and provide these values over some X extension". This is even more effort now that modesetting is in the kernel (back when nvtv was written, it wasn't). Without this, you are pretty much stuck with precalculated modes. Which isn't optimal, because with small overscan the timing gets a bit fickle, and with larger overscan you get the ugly border, and every analog TV is different in that respect. - Dirk _______________________________________________ Nouveau mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/nouveau
