> Hmm, I cannot use the tea6420 driver that comes with 'bttv' for four
> reasons:
>
> 1) It uses v4l-ioctls, while my driver is v4l2.
Hard to change as v4l2 isn't in the standard kernel, but bttv is.
I can't make bttv depend on something which isn't in the standard
kernel.
> 2) It only supports on tea6420 at adress 0x98, while my
> "Multimedia eXtension boards" has two tea6420s at
> adresses 0x98 and 0x9a.
Thats easy to fix I think.
> 3) It does not support to exactly specify which input should be
> connected to an output.
Hmm, the v4l interface allows to select a input only...
> 4) It depends on "bttv" (at least the header file is included).
It's just a few #defines for i2c addresses which are shared.
Easy to fix.
> I don't think it is a good solution to keep the driver so
> close to video4linux or bttv. The tea6420 (just like any other
> i2c-chipset) can be used in different environments and should
> be kept separated from other things.
Might be true for the tea6420 as it does just switching, but
is'nt for most others. There are i2c chips which do audio
processing (nicam/fm-stereo/sap decoding), for them it makes
absolutely no sense to use them in another environment than
TV / video4linux. Thats why I decided to simply pass throuth
the ioctls instead of inventing yet another interface for
every different chip. It has also the advantage that bttv
doesn't need to know any details about the helper chips.
One not-yet solved problem is to find a nice way to pass
around configuration informations like "this board has the
tuner on input #2" or "this board has chip foo at addr bar".
Gerd
--
To unsubscribe: mail [EMAIL PROTECTED] with
"unsubscribe" as the Subject.
