All of lore.kernel.org
 help / color / mirror / Atom feed
From: Antti Palosaari <crope@iki.fi>
To: Stephen Allan <stephena@intellectit.com.au>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>
Subject: Re: Hauppauge WinTV-HVR2205 driver feedback
Date: Wed, 03 Jun 2015 11:02:56 +0300	[thread overview]
Message-ID: <556EB4B0.8050505@iki.fi> (raw)
In-Reply-To: <556EB2F7.506@iki.fi>

On 06/03/2015 10:55 AM, Antti Palosaari wrote:
> On 06/03/2015 06:55 AM, Stephen Allan wrote:
>> I am aware that there is some development going on for the saa7164
>> driver to support the Hauppauge WinTV-HVR2205.  I thought I would post
>> some feedback.  I have recently compiled the driver as at 2015-05-31
>> using "media build tree".  I am unable to tune a channel.  When
>> running the following w_scan command:
>>
>> w_scan -a4 -ft -cAU -t 3 -X > /tmp/tzap/channels.conf
>>
>> I get the following error after scanning the frequency range for
>> Australia.
>>
>> ERROR: Sorry - i couldn't get any working frequency/transponder
>>   Nothing to scan!!
>>
>> At the same time I get the following messages being logged to the
>> Linux console.
>>
>> dmesg
>> [165512.436662] si2168 22-0066: unknown chip version Si2168-
>> [165512.450315] si2157 21-0060: found a 'Silicon Labs Si2157-A30'
>> [165512.480559] si2157 21-0060: firmware version: 3.0.5
>> [165517.981155] si2168 22-0064: unknown chip version Si2168-
>> [165517.994620] si2157 20-0060: found a 'Silicon Labs Si2157-A30'
>> [165518.024867] si2157 20-0060: firmware version: 3.0.5
>> [165682.334171] si2168 22-0064: unknown chip version Si2168-
>> [165730.579085] si2168 22-0064: unknown chip version Si2168-
>> [165838.420693] si2168 22-0064: unknown chip version Si2168-
>> [166337.342437] si2168 22-0064: unknown chip version Si2168-
>> [167305.393572] si2168 22-0064: unknown chip version Si2168-
>>
>>
>> Many thanks to the developers for all of your hard work.
>
> Let me guess they have changed Si2168 chip to latest "C" version. Driver
> supports only A and B (A20, A30 and B40). I have never seen C version.

gah, looking the driver I think that is not issue - it will likely print 
"unknown chip version Si2168-C.." on that case already. However, I 
remember I have seen that kind of issue earlier too, but don't remember 
what was actual reason. Probably something to do with firmware, wrong 
firmware and loading has failed? Could you make cold boot, remove socket 
from the wallet and wait minute it really powers down, then boot and 
look what happens.

regards
Antti



-- 
http://palosaari.fi/

  reply	other threads:[~2015-06-03  8:02 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03  3:55 Hauppauge WinTV-HVR2205 driver feedback Stephen Allan
2015-06-03  7:55 ` Antti Palosaari
2015-06-03  8:02   ` Antti Palosaari [this message]
2015-06-03  9:29     ` Olli Salonen
2015-06-03 14:30       ` Steven Toth
2015-06-04 12:46         ` Steven Toth
2015-06-03 15:34       ` Antti Palosaari
2015-06-03 19:08         ` Olli Salonen
2015-06-03 19:46           ` Antti Palosaari
2015-06-04  8:07             ` Olli Salonen
2015-06-04  0:38     ` Stephen Allan
2015-06-04  1:22       ` faulkner-ball
2015-06-03 14:31   ` Steven Toth
2015-06-03 21:50     ` Peter Faulkner-Ball
2015-06-03 22:16       ` Steven Toth
  -- strict thread matches above, loose matches on Subject: below --
2015-10-04  4:55 Richard Tresidder
2015-10-04 14:03 ` Steven Toth
2015-10-05  1:59   ` Richard Tresidder
2015-10-05 14:22     ` Steven Toth
2015-10-05 14:35       ` Richard Tresidder
2015-10-05 14:39         ` Richard Tresidder
2015-10-05 14:43         ` Steven Toth
2015-10-05 15:26           ` Richard Tresidder
2015-10-05 15:32             ` Steven Toth
2015-10-05 12:45 ` Tycho Lürsen
2015-10-05 14:22   ` Richard Tresidder
2015-10-05 16:03   ` Richard Tresidder
2015-10-11  6:18   ` Richard Tresidder
2015-10-11  7:33     ` Tycho Lürsen

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=556EB4B0.8050505@iki.fi \
    --to=crope@iki.fi \
    --cc=linux-media@vger.kernel.org \
    --cc=stephena@intellectit.com.au \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.