On Mon, Sep 03, 2001 at 07:27:51PM +0200, Gunther Mayer wrote:
> Marius Gedminas wrote:
> >
> > I'm trying to make a FlyVideo 98 card work under Linux without any
> > results. What tuner type should I use? There's a sticker on the card
> > saying "PAL-DK", but neither insmod tuner type=16 (Temic PAL_DK (4016
> > FY5)), nor type=23 (Philips PAL_DK) work. In fact I've unsuccessfully
> > tried all PAL tuner types.
>
> Can you provide the exact tuner type?
>
> If there is a sticker on the tuner try to spy through
> using striping light incidence or carefully remove it.
I'm afraid that's a little problematic -- almost everything is hidden in
a metal box. There are only two crystals (4 and 28 MHz) and one small
chip (Conexant Fusion 878A) outside that box.
A google search on "conexant fusion" reveals that this is a tv tuner
chip. Unless that 878 means it's actually a Brooktree Bt878 compatible.
> Please post "eeprom" output from "bttv/tools" directory
> ("insmod i2c-dev" if this lacks).
# modprobe i2c-dev
# ./eeprom
write addr /dev/i2c-0: Function not implemented
# ./eeprom -d /dev/i2c-1
write addr /dev/i2c-1: Remote I/O error
# ./eeprom -d /dev/i2c-2
write addr /dev/i2c-1: No such device
sensors-detect from lm-sensors detects two i2c adapters: SMBus PIIX4 and
bt848 #0, with one client at addres 0x61. However it fails to recognize
that client.
Some more experimenting:
# ./detect
0x5a: ??? (error: Device or resource busy)
0x90: ??? (error: Device or resource busy)
0x92: ??? (error: Device or resource busy)
0xa0: eeprom (bt878, Hauppauge-848) (error: Device or resource busy)
0xa2: ??? (error: Device or resource busy)
This looks like my SMBus PIIX4 adapter -- sensors-detect finds clients
at addresses 0x2d, 0x48, 0x49, 0x50, 0x51 (./detect doubles these
addresses), and 0x69.
# ./detect -d /dev/i2c-1
0xc2: tuner
sensors-detect calls this adapter Bt878, and finds a client on 0x61
(0xc2 = 0x61 << 1).
Now this `eeprom' client on i2c-0 address 0xa0 (or 0x50 according to
lm-sensors) appears to be one of my two SDRAM chips (the other is at
0xa2/0x51). And ./eeprom -d /dev/i2c-1 -a 0xc2 -x doesn't give very
meaningful results --
PCI Vendor ID: 0x3c3c, Subsystem ID: 0x3c3c
Decoding Hauppauge EEPROM:
Invalid eeprom(B1).
Marius Gedminas
--
Computers are not intelligent. They only think they are.
