Gerd Knorr wrote:
Gerd Knorr <kraxel@xxxxxxxxxxx> writes:
Next step is to build a config info table from that.
Initial try is in todays snapshot, probably needs some tweaks.
Comments welcome.
Gerd
Didn't work for me...
First issue:
gcc -I./../v4l2 -I. -D__KERNEL__ -I/usr/src/linux-2.4.20/include -Wall
-Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=i686
-DMODULE -nostdinc -iwithprefix include
-DKBUILD_BASENAME=saa7134_cards -c -o saa7134-cards.o saa7134-cards.c
saa7134-cards.c:572: duplicate array index in initializer
saa7134-cards.c:572: (near initialization for `fly_list')
saa7134-cards.c:575: warning: excess elements in array initializer
saa7134-cards.c:575: warning: (near initialization for `fly_list')
saa7134-cards.c:576: duplicate array index in initializer
saa7134-cards.c:576: (near initialization for `fly_list')
saa7134-cards.c:579: warning: excess elements in array initializer
saa7134-cards.c:579: warning: (near initialization for `fly_list')
saa7134-cards.c:580: duplicate array index in initializer
saa7134-cards.c:580: (near initialization for `fly_list')
saa7134-cards.c:583: warning: excess elements in array initializer
saa7134-cards.c:583: warning: (near initialization for `fly_list')
make[2]: *** [saa7134-cards.o] Error 1
make[2]: Leaving directory `/home/download/saa7134-0.2.7'
make[1]: *** [_mod_/home/download/saa7134-0.2.7] Error 2
make[1]: Leaving directory `/usr/src/linux-2.4.20'
make: *** [default] Error 2
Seems like ist doesn't like the:
/* default catch ... */
[ 0 ... 0x1f ] = {
.model = "UNKNOWN",
.tuner_type = TUNER_ABSENT,
},
I just changed the 0...0x1f to 0x0 to stop it catching... Maybe my
compiler doesn't like that syntax, or allocates all of 0x0..0x1f so when
you try and define 0x5, etc, it complains,
$ gcc -v
gcc version 2.95.4 20011002 (Debian prerelease)
Second issue:
# modprobe saa7134
doesn't work, since it doesn't detect a FlyVideo in any case - I don't
know if there is a case for catching this, maybe the lack on an eeprom?
This might get confused for other vendors that also don't detect an eeprom.
Trying again,
# modprobe saa7134 card=2
# dmesg
...
saa7134[0]: subsystem: 1131:0000, board: LifeView FlyVIDEO3000
[card=2,insmod option]
saa7134[0]: flyvideo: gpio is 0x38500 [model=PAL-BG,tuner=5]
tuner: chip found @ 0xc2
tuner: type set to 5 (Philips PAL_BG (FI1216 and compatibles))
i2c-core.o: client [Philips PAL_BG (FI1216 and compa] registered to
adapter [saa7134[0]](pos. 0).
...
Ok, well it detects based on the GPIO settings... Unfortunately, when I
said is was a PAL-BG tuner, I need to use modprobe saa7134 card=2
tuner=37. With the new snapshot, this doesn't work either since the case
0x05 still catches it, I remove (case 0x05) this and then try:
...
saa7134[0]: subsystem: 1131:0000, board: LifeView FlyVIDEO3000
[card=2,insmod option]
saa7134[0]: flyvideo: gpio is 0x38500 [model=<NULL>,tuner=0]
tuner: chip found @ 0xc2
tuner: type set to 0 (Temic PAL (4002 FH5))
i2c-core.o: client [Temic PAL (4002 FH5)] registered to adapter
[saa7134[0]](pos. 0).
...
Which stil isn't correct.
I can get it to work properly manually if I:
#modprobe tuner type=37
#modprobe saa7134 card=2
#dmesg
...
saa7134[0]: found at 02:04.0, rev: 1, irq: 5, latency: 32, mmio: 0xdf001000
saa7134[0]: subsystem: 1131:0000, board: LifeView FlyVIDEO3000
[card=2,insmod option]
saa7134[0]: flyvideo: gpio is 0x38500 [model=<NULL>,tuner=0]
tuner: chip found @ 0xc2
tuner(bttv): type forced to 37 (LG PAL (newer TAPC series)) [insmod]
tuner: type already set (37)
i2c-core.o: client [LG PAL (newer TAPC series)] registered to adapter
[saa7134[0]](pos. 0).
...
Somehow, we've got to decide whether it is a LG NEW TAPC PAL or a
Phillips PAL....
Rob
