Hi,
Just played with the latest saa7134-0.1.6 snapshot (Mar 27), and
it looks like the FlyVideo 2000 stuff is mostly there.
There's only one obvious remaining initialization bug I've found
at this point, due to the fact that my FV2K doesn't have FM radio.
(This affects saa7134-0.1.6 March 25th snapshot as well).
I believe that it happens in video_open(), during the test for the
presence of a radio device.
> if (h->radio_dev.minor == minor) {
> radio = 1;
> dev = h;
> }
Interestingly, the reordering of the inputs to put Television as the first
input entry triggers this bug. The symptom is that I'll not get any audio
until I switch inputs to Composite or SVideo, and then switch back to
Television. It does not trigger if Television is not the first input
entry.
The following is my dmesg-dump.
--- modprobe saa7134 ----------
saa7130/34: v4l2 driver version 0.1.6 loaded
PCI: Found IRQ 5 for device 00:09.0
saa7130[0]: found at 00:09.0, rev: 1, irq: 5, latency: 64, mmio: 0xe1001000
saa7130[0]: subsystem: 1131:0000, board: LifeView FlyVIDEO2000
saa7130[0]: gpio: mode=0x0006000 in=0x0030500 out=0x0000000 [pre-init]
saa7130[0]/video: set tv norm = PAL-BGHI
saa7130[0]/video: video input = 0 [Television]
saa7130[0]/video: set tv norm = PAL-BGHI
saa7130[0]/audio: ctl_mute=1 automute=0 input=Television => mute=1 input=mute
saa7130[0]: gpio: mode=0x0006000 in=0x0030500 out=0x0000000 [mute]
tuner: probing saa7130[0] i2c adapter [id=0x90000]
saa7130[0]/video: DCSDT: no signal
saa7130[0]/audio: tvaudio thread scan start [0]
tuner: chip found @ 0xc2
i2c-core.o: client [LG PAL (newer TAPC series)] registered to adapter [saa7130[0]](pos. 0).
i2c-core.o: adapter saa7130[0] registered as adapter 0.
saa7130[0]: Huh, no eeprom present (err=-5)?
saa7130[0]/video: DCSDT: no signal
saa7130[0]: registered device video0
saa7130[0]: registered device vbi0
saa7130[0]/video: DCSDT: found PAL
saa7130[0]/audio: tvaudio thread scan start [1]
saa7130[0]/video: DCSDT: found PAL
saa7130[0]/audio: tvaudio thread scan start [2]
saa7130[0]/audio: scanning 5.500 MHz => dc is 2740 [1906/-834]
saa7130[0]/audio: scanning 6.000 MHz => dc is 1256 [442/-814]
saa7130[0]/audio: scanning 6.500 MHz => dc is 463 [678/215]
saa7130[0]/audio: found PAL-BGHI main sound carrier @ 5.500 MHz
saa7130[0]/audio: tvaudio_setmode: trying PAL-B/G FM-stereo [5.500/5.742 MHz]
saa7130[0]/audio: tvaudio_setmode: trying PAL-B/G NICAM [5.500/5.850 MHz]
saa7130[0]/audio: tvaudio_setmode: using PAL-B/G FM-stereo [5.500/5.742 MHz]
--- after xawtv -noxv ------
saa7130[0]/video: open minor=0 radio=1
saa7130[0]/video: open minor=0 radio=1
^^^^^^^ I don't have a radio!
saa7130[0]/audio: ctl_mute=0 automute=0 input=<NULL> => mute=0 input=<NULL>
saa7130[0]: gpio: mode=0x0006000 in=0x0030500 out=0x0000000 [<NULL>]
saa7130[0]/audio: ctl_mute=1 automute=0 input=<NULL> => mute=1 input=mute
saa7130[0]: gpio: mode=0x0006000 in=0x0030500 out=0x0000000 [mute]
saa7130[0]/video: set tv norm = PAL-BGHI
saa7130[0]/audio: ctl_mute=0 automute=0 input=<NULL> => mute=0 input=<NULL>
saa7130[0]: gpio: mode=0x0006000 in=0x0030500 out=0x0000000 [<NULL>]
Audio path selection is confused ^^^^^^^^
(This probably happens when xawtv does a video_open() and causes
it to select a radio input).
----------------------
Another artifact I observed is that the video picture doesn't always
get displayed in the XServer until I click in the xawtv window.
Other than that, I guess there's some cleanup that can be done for
set_tvnorm() in saa7134-video.c since it's now called from within
video_mux(). video_mux() and set_tvnorm() pairs are found together
in several places.
PS. I'm a little busy these few days so I don't have time to try and
come up with a bugfix for this.
Regards,
T.C.
----
Wan Tat Chee (Lecturer)
School of Computer Science, Univ. Science Malaysia,
11800 Minden, Penang, Malaysia. Ofc Ph: +604 657-7888 x 3617
Internet: tcwan@xxxxxxxxx Web: http://nrg.cs.usm.my/~tcwan
GPG Key : http://nrg.cs.usm.my/~tcwan/tcw_gpg.asc
F'print : FB0F CED7 85A5 ECF9 DEF0 50E8 A550 A0D2 8638 B1EB
