From: Hans de Goede <hdegoede@redhat.com>
To: Antti Palosaari <crope@iki.fi>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
hverkuil@xs4all.nl
Subject: Re: [PATCH 4/4] radio-si470x: Lower firmware version requirements
Date: Mon, 09 Jul 2012 15:02:30 +0200 [thread overview]
Message-ID: <4FFAD666.5060402@redhat.com> (raw)
In-Reply-To: <4FFAC75B.5060506@iki.fi>
Hi,
On 07/09/2012 01:58 PM, Antti Palosaari wrote:
> On 07/09/2012 01:03 PM, Hans de Goede wrote:
> If I tune using old radio it works. If I tune using latest radio but with option -l 0 (./console/radio -l 0) it also works. Using "arecord -D hw:2,0 -r96000 -c2 -f S16_LE | aplay -" to listen. So it seems that latest radio with alsa loopback is only having those problems.
>
Ok.
>
> These are the patches:
> radio-si470x: Don't unnecesarily read registers on G_TUNER
> radio-si470x: Lower hardware freq seek signal treshold
> radio-si470x: Always use interrupt to wait for tune/seek completion
> radio-si470x: Lower firmware version requirements
>
> And from that I can see it loads new driver as it does not warn about software version - only firmware.
Right, so what I want to do is to lower the firmware requirement to 12, so that it won't complain
for your device since that seems to be working fine. Does that sound like a good idea to you?
> Jul 9 14:28:29 localhost kernel: [13403.017920] Linux media interface: v0.10
> Jul 9 14:28:29 localhost kernel: [13403.020866] Linux video capture interface: v2.00
> Jul 9 14:28:29 localhost kernel: [13403.022744] radio-si470x 5-2:1.2: DeviceID=0x1242 ChipID=0x060c
> Jul 9 14:28:29 localhost kernel: [13403.022747] radio-si470x 5-2:1.2: This driver is known to work with firmware version 14,
> Jul 9 14:28:29 localhost kernel: [13403.022749] radio-si470x 5-2:1.2: but the device has firmware version 12.
> Jul 9 14:28:29 localhost kernel: [13403.024715] radio-si470x 5-2:1.2: software version 1, hardware version 7
> Jul 9 14:28:29 localhost kernel: [13403.024717] radio-si470x 5-2:1.2: If you have some trouble using this driver,
> Jul 9 14:28:29 localhost kernel: [13403.024719] radio-si470x 5-2:1.2: please report to V4L ML at linux-media@vger.kernel.org
> Jul 9 14:28:29 localhost kernel: [13403.114583] usbcore: registered new interface driver radio-si470x
Regards,
Hans
next prev parent reply other threads:[~2012-07-09 13:02 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 13:43 [PATCH 1/4] radio-si470x: Don't unnecesarily read registers on G_TUNER Hans de Goede
2012-06-14 13:43 ` [PATCH 2/4] radio-si470x: Always use interrupt to wait for tune/seek completion Hans de Goede
2012-06-14 13:43 ` [PATCH 3/4] radio-si470x: Lower hardware freq seek signal treshold Hans de Goede
2012-06-14 13:43 ` [PATCH 4/4] radio-si470x: Lower firmware version requirements Hans de Goede
2012-07-04 15:23 ` Antti Palosaari
2012-07-05 8:33 ` Hans de Goede
2012-07-05 13:35 ` Antti Palosaari
2012-07-05 13:41 ` Hans de Goede
2012-07-05 14:13 ` Antti Palosaari
2012-07-05 15:08 ` Hans de Goede
2012-07-05 15:09 ` Antti Palosaari
2012-07-07 7:58 ` Hans de Goede
2012-07-07 9:00 ` Antti Palosaari
2012-07-07 18:53 ` Hans de Goede
2012-07-09 9:17 ` Antti Palosaari
2012-07-09 10:03 ` Hans de Goede
2012-07-09 11:58 ` Antti Palosaari
2012-07-09 13:02 ` Hans de Goede [this message]
2012-07-09 13:34 ` Antti Palosaari
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=4FFAD666.5060402@redhat.com \
--to=hdegoede@redhat.com \
--cc=crope@iki.fi \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@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;
as well as URLs for NNTP newsgroup(s).