[linux-dvb] DViCO FusionHDTV DVB-T Lite frontend driver issue

Markus Rechberger mrechberger at gmail.com
Thu Apr 6 19:14:34 CEST 2006


Hi,

0x14 is the returnvalue of a Zarlink/Intel ZL10353 based device not a
Zarlink MT352 DVB-T demodulator.

Markus

On 4/6/06, Martin Petrovsky <mpetrovsky at swiftdsl.com.au> wrote:
>  Hello Chris,
>
>  I've just brought a DViCO FusionHDTV DVB-T Lite card (lspci attached) and
> I'm having a few problems getting it to work. I was hoping on some advice.
>
>  I don't have much experience with dvb under linux, so I apologise for any
> ignorance.
>
>  I'm using kernel 2.6.16 with your hg-pascoe tree on top. I'm loading the
> following modules
>
>  modprobe bttv
>  modprobe mt352 debug=1
>  modprobe cx88-dvb debug=8
>  modprobe dst verbose=8
>  modprobe dvb_bt8xx debug=8
>
>  I'm getting the following log
>
>  <3>i2c_core: Unknown parameter `debug'
>  <6>Linux video capture interface: v1.00
>  <7>i2c-core: driver [tveeprom] registered
>  <6>bttv: driver version 0.9.16 loaded
>  <6>bttv: using 8 buffers with 2080k (520 pages) each for capture
>  <6>bttv: Bt8xx card found (0).
>  <6>bttv0: Bt878 (rev 17) at 0000:03:08.0, irq: 10, latency: 32, mmio:
> 0xfdcff000
>  <6>bttv0: detected: DViCO FusionHDTV DVB-T Lite [card=128], PCI subsystem
> ID is 18ac:db10
>  <6>bttv0: using: DViCO FusionHDTV DVB-T Lite [card=128,autodetected]
>  <7>bttv0: gpio: en=00000000, out=00000000 in=00ffffff [init]
>  <7>i2c_adapter i2c-0: adapter [bt878 #0 [sw]] registered
>  <7>i2c_adapter i2c-0: found normal entry for adapter 0, addr 0x50
>  <7>i2c_adapter i2c-0: master_xfer[0] W, addr=0x50, len=0
>  <7>i2c_adapter i2c-0: master_xfer[0] W, addr=0x50, len=0
>  <7>i2c_adapter i2c-0: client [tveeprom] registered with bus id 0-0050
>  <4>bttv0: using tuner=-1
>  <4>bttv0: add subdevice "dvb0"
>  <6>cx2388x dvb driver version 0.0.5 loaded
>  <6>bt878: AUDIO driver version 0.0.0 loaded
>  <6>bt878: Bt878 AUDIO function found (0).
>  <4>bt878_probe: card id=[0xdb1018ac],[ DViCO FusionHDTV DVB-T Lite ] has
> DVB functions.
>  <6>bt878(0): Bt878 (rev 17) at 03:08.1, irq: 10, latency: 32, memory:
> 0xfdcfe000
>  <7>dvb_bt8xx: identified card0 as bttv0
>  <4>DVB: registering new adapter (bttv0).
>  <7>mt352: mt352_attach: hello
>  <7>i2c_adapter i2c-0: master_xfer[0] W, addr=0x0f, len=1
>  <7>i2c_adapter i2c-0: master_xfer[1] R, addr=0x0f, len=1
>  <7>i2c_adapter i2c-0: master_xfer[0] W, addr=0x0f, len=1
>  <7>i2c_adapter i2c-0: master_xfer[1] R, addr=0x0f, len=1
>  <7>mt352: MJP -- mt352_read_register error. Exiting - 0014
>  <4>dvb-bt8xx: A frontend driver was not found for device 109e/0878
> subsystem 18ac/db10 type 0080
>
>  It looks like it's bailing out at mt352_attach . The call to
> mt352_read_register seams to be returning 0x14 not the expected ID_MT352
> (0x13).
>  Does this mean that the card I got has a different front end or something?
>
>  // mt352.c   mt352_read_register  line 550
>          /* setup the state */
>          state->i2c = i2c;
>          memcpy(&state->config,config,sizeof(struct
> mt352_config));
>          memcpy(&state->ops, &mt352_ops, sizeof(struct dvb_frontend_ops));
>
>          /* check if the demod is there */
>          if (mt352_read_register(state, CHIP_ID) != ID_MT352) {
>                  dprintk("MJP -- mt352_read_register error. Exiting -
> %04x\n", mt352_read_register(state, CHIP_ID));
>                  goto error;
>          }
>
>  I also noticed a "bttv0: using tuner=-1" message above. Is this related?
>
>  Any help would be appreciated,
>
>  Thanks
>
>  Martin P
> _______________________________________________
> linux-dvb mailing list
> linux-dvb at linuxtv.org
> http://www.linuxtv.org/cgi-bin/mailman/listinfo/linux-dvb
>
>
>


--
Markus Rechberger



More information about the linux-dvb mailing list