From: Simon Farnsworth <simon.farnsworth@onelan.com>
To: Andy Walls <awalls@radix.net>
Cc: linux-media@vger.kernel.org
Subject: Re: Poor reception with Hauppauge HVR-1600 on a ClearQAM cable feed
Date: Thu, 15 Oct 2009 09:58:16 +0100 [thread overview]
Message-ID: <4AD6E428.1060006@onelan.com> (raw)
In-Reply-To: <1255576352.5829.16.camel@palomino.walls.org>
Andy Walls wrote:
> Right, the windows driver code for the mxl5005s is better. Inform him
> that the linux driver for the mxl5005s could be better. If he has any
> contacts at MaxLinear to get the datasheet and programming manual
> released to me, I can make the linux driver better.
>
We don't have contacts that we know of, but we're happy to chase after a
datasheet for you if Devin's copy isn't enough - just let me know.
>
> The MXL5005s is the silicon tuner chip on the Digital TV side of the
> HVR-1600. A simple picture for you:
>
> Cable ---| MXL5005s |----| CX24227 |----| CX23418 |--- PCI bus
>
> ---- Analog Waveform-----------|--------Digital Data--------------
>
That's nice and clear, and explains things to me perfectly. Thank you.
>
> Here's my HVR-1600 related entries from dmesg on startup. I have the
> MXL5005S showing up at 9.510:
>
> [ 9.510767] MXL5005S: Attached at address 0x63
So basically, I was being blind and/or stupid - with this to hand, I've
found the equivalent message in my dmesg.
--
Simon Farnsworth
prev parent reply other threads:[~2009-10-15 8:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-14 8:54 Poor reception with Hauppauge HVR-1600 on a ClearQAM cable feed Simon Farnsworth
2009-10-14 10:35 ` Andy Walls
2009-10-14 11:01 ` Simon Farnsworth
2009-10-14 13:14 ` Devin Heitmueller
2009-10-15 3:12 ` Andy Walls
2009-10-15 3:32 ` Devin Heitmueller
2009-10-15 8:58 ` Simon Farnsworth [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=4AD6E428.1060006@onelan.com \
--to=simon.farnsworth@onelan.com \
--cc=awalls@radix.net \
--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.