Wan Tat Chee wrote: > > Gunther, > > Gerd's saa7134-0.1.5 (the March 11 snapshot) doesn't change the way > that FlyVideo3000 works. The main differences are with the FlyVideo 2000 > support, as all my audio input comes via LINE2 of the SAA7130. > > It looks like you have a similar TV Tuner block to mine (except for the > FM Radio). How did you manage to get it to work with the existing > definition for FV3K? Did you modprobe the tuner type manually? My FlyVideo 3000 (from Alternate) works out of the box, this includes: - picture quality is very good - correct tuner (PAL as in the fixed entry in "saa7134-cards.c") Other Flyvideocards encoded their tuner type in GPIO (see bttv-0.7.91), so probably this could be autodetected, too. Gerd, it would be very helpful to printk GPIO input values on insmod. - tv stereo - radio - Volume control (external active speakers) - Mute/Unmute Untested: - Audio In - Videotext minor Problems: - TV and radio can be started simultaneously and distort each other - even when started sequentially tv sound doesn't work at first (switching channels or re-starting xawtv helps) - tv sound doesn't work when switching from external video back to tv (same workaround as above) - Brightness Pumping on some channels (about one time a second the picture slowly gets brighter and suddenly dark; then it starts anew) Gerd is there some "automatic brighness(/gain?) control in SAA7134 ? - on insmod I get Mar 22 22:18:17 m3 kernel: saa7134[0]: i2c eeprom read error #1 rc=-5 - the entry concerning external video sources misses my CVideo and assumes CVideo on the SVideo connector (fine if you have an adapter). Patch follows. - "radio" signal quality and mono/stereo indicator don't work - What the heck is the hef4052bt on my card used for? Regards, Gunther
