Re: bttv 0.9.19 driver

Re: bttv 0.9.19 driver

[Mauro Carvalho Chehab]

Hi Paulo,

Em 23-03-2012 07:14, Paulo Cavalcanti escreveu:
> 
> Hi,
> 
> I have been using an analog bttv capture card (a Pixelview PV-M4900 FM.RC - PV-BT878P+ (Rev.4C,8E)) since 2006 with these parameters
> in modprobe.conf:
> 
> options bttv card=70 radio=1 tuner=69 audiomux=0x21,0x20,0x23,0x23,
> 0x28 gpiomask=0x3f vcr_hack=1 chroma_agc=1
> 
> However, since RHLE6 start shipping the kernel-2.6.32-220 series, the radio does not work any more (the TV is fine, though).
> 
> I have another computer running Fedora with kernel 2.6.35.14 with the same card, and
> I tried to update video4linux to the newest snapshot and the same thing happened.
> In /var/log/messages I only see these differences:
> 
> bttv driver 0.9.18 <----- work
> 
> tuner 1-0061: chip found @ 0xc2 (bt878 #0 [sw])
> Mar 19 17:24:43 cascavel kernel: [    8.332740] tuner-simple 1-0061: creating new instance
> Mar 19 17:24:43 cascavel kernel: [    8.332744] tuner-simple 1-0061: type set to 69 (Tena TNF 5335 and similar models)
> 
> 
> bttv driver 0.9.19 <------ broke
> 
> Mar 21 18:18:55 cascavel kernel: [    6.492175] tuner 1-0061: Tuner -1 found with type(s) Radio TV.
> Mar 21 18:18:55 cascavel kernel: [    6.533837] tuner-simple 1-0061: creating new instance
> Mar 21 18:18:55 cascavel kernel: [    6.533841] tuner-simple 1-0061: type set to 69 (Tena TNF 5335 and similar models)
> 
> The rest of the log is the same:
> 
> bttv: driver version 0.9.19 loaded
> Mar 21 21:44:36 cascavel kernel: [    7.978998] bttv: using 8 buffers with 2080k (520 pages) each for capture
> Mar 21 21:44:36 cascavel kernel: [    7.979161] bttv: Bt8xx card found (0)
> Mar 21 21:44:36 cascavel kernel: [    7.979186] bttv 0000:04:00.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
> Mar 21 21:44:36 cascavel kernel: [    7.979195] bttv: 0: Bt878 (rev 17) at 0000:04:00.0, irq: 21, latency: 32, mmio: 0xe3101000
> Mar 21 21:44:36 cascavel kernel: [    7.979227] bttv: 0: detected: Prolink Pixelview PV-BT [card=72], PCI subsystem ID is 1554:4011
> Mar 21 21:44:36 cascavel kernel: [    7.979230] bttv: 0: using: Prolink Pixelview PV-BT878P+ (Rev.4C,8E) [card=70,insmod option]
> Mar 21 21:44:36 cascavel kernel: [    7.979232] bttv: 0: gpio config override: mask=0x3f, mux=0x21,0x20,0x23,0x23
> Mar 21 21:44:36 cascavel kernel: [    7.979319] bttv: 0: tuner type=69
> 
> It is like I could not change the radio stations any more, because I only hear noise, and some times the last TV channel
> synchronized.
> 
> Does anyone know if anything has changed in the new bttv driver?

There was a known regression at the radio core. Not sure when it happened, nor on what
kernel it were fixed. Could you please test a 3.x kernel?

If you're a RHEL6 customer, you can open a case with via the proper
Red Hat channels, in order to backport fix it on RHEL6 kernel.
Yet, even in this case, it would be important to test the latest kernel,
to see if the fixes applied upstream fixes the issue.

Thanks,
Mauro.

Re: bttv 0.9.19 driver

[Mauro Carvalho Chehab]

Em 25-03-2012 09:21, Paulo Cavalcanti escreveu:
> 
> 
> 
> 
>     There was a known regression at the radio core. Not sure when it happened, nor on what
>     kernel it were fixed. Could you please test a 3.x kernel?
> 
>     If you're a RHEL6 customer, you can open a case with via the proper
>     Red Hat channels, in order to backport fix it on RHEL6 kernel.
>     Yet, even in this case, it would be important to test the latest kernel,
>     to see if the fixes applied upstream fixes the issue.
> 
>     Thanks,
>     Mauro.
> 
> 
> Hi, Mauro
> 
> I tested other card ids, and the one that has always been chosen by the kernel (72) is working now:
> 
> options bttv card=72 radio=1 tuner=69 audiomux=0x21,0x20,0x23,0x23,0x28 gpiomask=0x3f vcr_hack=1 chroma_agc=1
> 
> In the past, this combination of tuner and card id had problems with the TV sound,
> but now either the radio, tv or remote is fine. I only did not test the composite input of the card.

Good.

> However, this is enough for me to maintain the analog radio packages in Fedora.
> 
> Regarding the 3.0 kernel, If I update the video4linux drivers to the latest snapshot (in my case 03/21/2012) doesn't it produce the same result?

It should produce the same results.

> I am also trying to keep rhel6 functional in ATrpms, and I realized that there was also some recent
> change (after 11/24/2011) that forced me to upgrade video4linux drivers to have
> vlc 2.0 working with ISDB-TB in previous kernels:
> 
> http://forum.videolan.org/viewtopic.php?f=13&t=99397 <http://forum.videolan.org/viewtopic.php?f=13&t=99397>

ISDB-T works on older kernels, via an emulation code at the Kernel. Userspace apps
thinks ISDB is DVB-T, so they all work.

The only think that doesn't work, via the emulation code, is radio broadcast. There are some
DVBv5 properties that need to be filled for it:

#define DTV_ISDBT_SOUND_BROADCASTING	19

#define DTV_ISDBT_SB_SUBCHANNEL_ID	20
#define DTV_ISDBT_SB_SEGMENT_IDX	21
#define DTV_ISDBT_SB_SEGMENT_COUNT	22

As there's no equivalent of those on DVB-T, and those parameters aren't automatically
detected by the (current) frontendds. So, only a program prepared to use them would
work. Also, not all ISDB drivers are prepared to work with those properties.

I never tested radio broadcast, as there aren't any such stations in Brazil,
so I can't tell if it works or not.

> I know this is a different topic, but would you know if mplayer is supporting ISDB-TB?

AFAIKT, mplayer doesn't support DVBv5 API, but, provided that you feed it with a proper
channels.conf file under ~/.mplayer, it works fine.

> While vlc and xine/kaffeine work, gstreamer and mplayer are still not working with ISDB-TB for me ...

Never tested gstreamer with ISDB-T.
> 
> Thanks.
> 
> -- 
> Paulo Roma Cavalcanti
> LCG - UFRJ