Mailing List archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[linux-dvb] Re: Avermedia DVB-T bttv [hw] or [sw]



David Maslen <dmm_au@yahoo.com> writes:

> I have a Avermedia DVB-T card working under linux 2.6.7 (with bttv
> patches from bytesex.org for latest bttv driver)
> It's not completely stable, but when it falls over, reloading the bttv
> driver gets it going again.
>
> dmesg output looks like this;
> bttv: driver version 0.9.15 loaded
> bttv: using 8 buffers with 2080k (520 pages) each for capture
> bttv: Host bridge needs ETBF enabled.
> bttv: Bt8xx card found (0).
> bttv0: Bt878 (rev 17) at 0000:00:0d.0, irq: 3, latency: 64, mmio: 0xd7000000
> bttv0: detected: AverMedia AverTV DVB-T [card=104], PCI subsystem ID is 1461:0761
> bttv0: using: Nebula Electronics DigiTV [card=104,autodetected]
> bttv0: enabling ETBF (430FX/VP3 compatibilty)
> bttv0: risc main @ 170be000
> bttv0: gpio: en=00000000, out=00000000 in=0098004d [init]
> i2c-algo-bit.o: (0) scl=1, sda=1
> i2c-algo-bit.o: (1) scl=1, sda=0
> i2c-algo-bit.o: (2) scl=1, sda=1
> i2c-algo-bit.o: (3) scl=0, sda=1
> i2c-algo-bit.o: (4) scl=1, sda=1
> i2c-algo-bit.o: bt878 #0 [sw] passed test.
> bttv0: using tuner=-1
> bttv0: registered device video0
> bttv0: registered device vbi0
> bttv0: video mux: input=0 mux=2
> bttv0: PLL: 28636363 => 35468950 .. ok
> bttv0: add subdevice "dvb0"
> bt878: AUDIO driver version 0.0.0 loaded
> bt878: Bt878 AUDIO function found (0).
> bt878(0): Bt878 (rev 17) at 00:0d.1, irq: 3, latency: 64, memory: 0xd6800000
> attach: checking "bt878 #0 [sw]"
> find by pci: checking "bt878 #0 [sw]"
> attach: "bt878 #0 [sw]", to card 0
> DVB: registering new adapter (Ave).
> DVB: registering frontend 0:0 (Microtune MT7202DTF)...
>
> If I change my /etc/modprobe.conf to include;
> options bttv            bttv_verbose=2 bttv_debug=1 card=0x68 i2c_hw=1
>
> Then I can't start my frontend with either mplayer of tzap.
>
> Everything I've found via google, suggests I should be using the
> i2c_hw=1 option. I'm keen to see whether I'll get my reliable
> encoding this way.





Home | Main Index | Thread Index