linux-media.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Hans de Goede <hdegoede@redhat.com>
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 16:34:34 +0300	[thread overview]
Message-ID: <4FFADDEA.3000808@iki.fi> (raw)
In-Reply-To: <4FFAD666.5060402@redhat.com>

Hello

On 07/09/2012 04:02 PM, Hans de Goede wrote:
> 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?

Yes, indeed lower it to the 12 as it works to get rid of those warnings. 
It still cracks but rarely, once per 2 mins or so when using arecord + 
aplay.


The whole journey of playing that device was idea to learn V4L2 radio 
API as I was planning to add SDR functionality. Anyhow, I am a little 
bit disappointed because that radio uses snd-usb-audio module for audio. 
Do you know any cheap usb radio which uses vendor specific USB 
interface, not standard profiles?


regards
Antti


-- 
http://palosaari.fi/



      reply	other threads:[~2012-07-09 13:34 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
2012-07-09 13:34                             ` Antti Palosaari [this message]

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=4FFADDEA.3000808@iki.fi \
    --to=crope@iki.fi \
    --cc=hdegoede@redhat.com \
    --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).