> 3. Updating the saa7134-cards.c cards entry is not reflected properly > via 'v4lctl list' after a 'rmmod saa7134 tuner v4l2-common ...' while > running under XWindows. E.g., while modprobing the official > saa7134-0.1.5 module vs. my modified saa7134-0.1.5-fv2k module, the > availability of the S-Video input is not updated properly. Sounds like you are using Xvideo. The X-Server reads this info only once at startup. Try "-noxv" or "-c /dev/video<n>" to make xawtv talk to the device directly. > 4. vbi support on FV2K still not functional. 'alevtd -d' after I've tuned > into the correct TV channel complains about "insufficient number of > periods..." Known issue. Not sure whenever this is a driver or application issue. The saa7134 uses another sample rate than the bt848 cards, might be the vbi decoding algorithms are fine-tuned for the bt848. alevtd's vbi code often recognises the start sequences, but bails out early while decoding the line with hamm errors. > + if (dev->ctl_mute || dev->automute) > + saa_andorb(SAA7134_ANALOG_IO_SELECT, 0x07, 0x00); /* LINE1 */ I still think this is _wrong_. TV cards usually have a line-out and a line-in. The line-out can be connected to your sound-cards line-in, and whatever was in your sound-cards line-in before can be plugged into the tv-cards line-in now. The LINE1 input was designed to do exactly that (power-on default is to simply pass throught the signal from LINE1 to the audio output), and I suspect the only reason that the above mutes the card for you is that you don't have anything connected to the tv cards line-in. Gerd -- #include </dev/tty>
