public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Toth <stoth@kernellabs.com>
To: seth@cyberseth.com
Cc: Steve Harrington <steve@Emel-Harrington.net>,
	linux-media@vger.kernel.org
Subject: Re: Hauppauge 2250 - second tuner is only half working
Date: Tue, 25 Aug 2009 20:19:21 -0400	[thread overview]
Message-ID: <4A947F89.3010705@kernellabs.com> (raw)
In-Reply-To: <4A947260.1040907@kernellabs.com>

On 8/25/09 7:23 PM, Steven Toth wrote:
> On 8/25/09 6:59 PM, Steven Toth wrote:
>>> After reading Steven Toth's reply I tried adding 1 and then 2 2-way
>>> splitters before the 2250 input. No joy. I also tried feeding the cable
>>> directly into the 2250 with no splitters. Again - no joy.
>>> Any other ideas?
>>
>> Most likely this is dependent on what frequency the other tuner is tuned
>> to, especially since Seth indicated it worked for a short time. And,
>> again, I don't see the issue but two other people do.
>>
>> RMA is probably not the answer.
>>
>> When you next get a chance to test please use azap and keep track of
>> what frequency the first tuner is currently tuned to even if tuner#1 is
>> technically no longer streaming. I suspect varying the frequency on
>> tuner#1 will vary your test results.
>>
>
> OK, I can repro the issue.
>
> Tuning tuner 1 to 669 works, then tune tuner2 to 669 no lock. Set tuner
> #1 to 579 is locks, then tuner2 automatically also goes into lock.
>
> So, it depends on where tuner#1 was previously tuned to.
>
> I'll look into this.
>
> Save yourself the trouble of the RMA if it hasn't already shipped.
>

I was able to repro the issue once however during patching the issue went away, 
never to return - regardless of whether the patch was active or not. I even ran 
a series of cold boots to try and repro the behavior but I cannot.

I have seen the issue and I believe it exists, I just cannot get a reliable repro.

If you can test tuner 1 on selected frequencies then test tuner 2 always against 
channel 103 (669MHz) and find a reliable repro case then I'll take another look.

Annoying.

-- 
Steven Toth - Kernel Labs
http://www.kernellabs.com

  reply	other threads:[~2009-08-26  0:19 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-25 22:31 Hauppauge 2250 - second tuner is only half working seth
2009-08-25 22:59 ` Steven Toth
2009-08-25 23:23   ` Steven Toth
2009-08-26  0:19     ` Steven Toth [this message]
2009-08-26  2:18       ` seth
2009-08-26 13:13         ` Steven Toth
  -- strict thread matches above, loose matches on Subject: below --
2009-08-25 21:01 Steve Harrington
2009-08-17  7:07 seth
2009-08-18 12:23 ` Steven Toth
2009-08-19 14:12   ` seth
2009-08-19 22:41     ` Andy Walls
2009-08-20 12:59     ` Steven Toth

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=4A947F89.3010705@kernellabs.com \
    --to=stoth@kernellabs.com \
    --cc=linux-media@vger.kernel.org \
    --cc=seth@cyberseth.com \
    --cc=steve@Emel-Harrington.net \
    /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