From: Roman Savochenko <rom_as@oscada.org>
To: linux-kernel@vger.kernel.org
Subject: Regression-broken V4L2 radio API for BTTV cards (PV951)
Date: Thu, 15 Dec 2011 14:41:44 +0200 [thread overview]
Message-ID: <4EE9EB08.7060701@oscada.org> (raw)
Hello, All
Start from kernel 2.6.39 my TV card's PV951 radio is not work.
On 2.6.38 it still fine work and form 2.6.39 to present it is not.
I have seen to source's different for BTTV code from 2.6.38 to 2.6.39
and have not seen any functional changes then the problem is generic for
radio API.
For test I call command "v4l2-ctl -d /dev/radio --all -L" on 2.6.32 and
3.1.4 kernel's versions:
***************** 2.6.32 (OK) *************************
[root@roman ~]# v4l2-ctl -d /dev/radio --all -L
Driver Info (not using libv4l2):
Driver name : bttv
Card type : BT878 radio (ProVideo PV951)
Bus info : PCI:0000:01:09.0
Driver version: 0.9.18
Capabilities : 0x00010000
Tuner
Video input : 0 (Radio: ok)
Audio input : 0 (Radio)
Frequency: 1040500 (65.031250 MHz)
Tuner:
Name : Radio
Capabilities : 62.5 Hz stereo
Frequency range : 65.0 MHz - 108.0 MHz
Signal strength/AFC : 13%/0
Current audio mode : stereo
Available subchannels: mono
mute (bool) : default=0 value=0
***************** 3.1.4 (Wrong) *************************
[root@roman ~]# v4l2-ctl -d /dev/radio --all -L
Driver Info (not using libv4l2):
Driver name : bttv
Card type : BT878 radio (ProVideo PV951)
Bus info : PCI:0000:01:09.0
Driver version: 3.1.4
Capabilities : 0x00010000
Tuner
Video input : 0 (Radio: ok)
Audio input : 0 (Radio)
Frequency: 0 (0.000000 MHz)
Tuner:
Name : Radio
Capabilities : 62.5 kHz
Frequency range : 0.0 MHz - 0.0 MHz
Signal strength/AFC : 0%/0
Current audio mode : mono
Available subchannels:
mute (bool) : default=0 value=0
Regards, Roman
next reply other threads:[~2011-12-15 12:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-15 12:41 Roman Savochenko [this message]
2012-05-14 7:32 ` Regression-broken V4L2 radio API for BTTV cards (PV951) Roman Savochenko
2012-05-14 17:17 ` Roman Savochenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4EE9EB08.7060701@oscada.org \
--to=rom_as@oscada.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox