From: Steven Toth <stoth@kernellabs.com>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: David Ward <david.ward@gatech.edu>, linux-media@vger.kernel.org
Subject: Re: cx18, s5h1409: chronic bit errors, only under Linux
Date: Tue, 09 Jun 2009 10:24:35 -0400 [thread overview]
Message-ID: <4A2E70A3.7070002@kernellabs.com> (raw)
In-Reply-To: <829197380906090723t434eef6dje1eb8a781babd5c7@mail.gmail.com>
Devin Heitmueller wrote:
> On Tue, Jun 9, 2009 at 10:21 AM, Steven Toth <stoth@kernellabs.com> wrote:
>> I ruled out 30db on ATSC because that sounds incredibly high, I assumed
>> cable because that would be consistent with the numbers. You could well be
>> right.
>>
>> --
>> Steven Toth - Kernel Labs
>> http://www.kernellabs.com
>
> I agree it's high, but certainly possible. I've got a 30 dB signal,
> but my situation is a bit unusual.
>
> I spent all of last night working on another issue, but I am hoping to
> get back to it this week.
David has called out Comcast to review his installation.
--
Steven Toth - Kernel Labs
http://www.kernellabs.com
next prev parent reply other threads:[~2009-06-09 14:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-08 10:31 cx18, s5h1409: chronic bit errors, only under Linux David Ward
2009-06-08 14:14 ` Steven Toth
2009-06-08 14:17 ` Devin Heitmueller
2009-06-08 16:20 ` David Ward
2009-06-08 16:31 ` Steven Toth
2009-06-08 17:16 ` David Ward
2009-06-08 20:20 ` Steven Toth
2009-06-08 20:36 ` Devin Heitmueller
2009-06-08 21:03 ` David Ward
2009-06-08 21:09 ` Devin Heitmueller
2009-06-09 14:23 ` Steven Toth
2009-06-09 14:21 ` Steven Toth
2009-06-09 14:23 ` Devin Heitmueller
2009-06-09 14:24 ` Steven Toth [this message]
2009-06-09 18:52 ` David Ward
2009-06-09 18:55 ` Devin Heitmueller
2009-06-09 19:04 ` Steven Toth
2009-06-09 19:07 ` Devin Heitmueller
2009-06-09 19:26 ` Steven Toth
2009-06-10 8:11 ` David Ward
2009-06-10 14:32 ` Steven Toth
2009-06-11 21:27 ` David Ward
2009-06-09 19:05 ` Steven Toth
2009-06-09 2:44 ` Andy Walls
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=4A2E70A3.7070002@kernellabs.com \
--to=stoth@kernellabs.com \
--cc=david.ward@gatech.edu \
--cc=dheitmueller@kernellabs.com \
--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 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.