From: Simon Farnsworth <simon.farnsworth@onelan.com>
To: Andy Walls <awalls@md.metrocast.net>
Cc: Steven Toth <stoth@kernellabs.com>,
LMML <linux-media@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>,
Michael Krufky <mkrufky@kernellabs.com>
Subject: Re: Problems tuning PAL-D with a Hauppauge HVR-1110 (TDA18271 tuner) - workaround hack included
Date: Mon, 3 Oct 2011 09:57:58 +0100 [thread overview]
Message-ID: <201110030957.58627.simon.farnsworth@onelan.com> (raw)
In-Reply-To: <ce2d195e-f23b-4ac4-b149-15b09b53a942@email.android.com>
On Friday 30 September 2011, Andy Walls <awalls@md.metrocast.net> wrote:
> Steven Toth <stoth@kernellabs.com> wrote:
> >The TDA18271 driver on linux DOES NOT use the same I/F's that the
> >windows driver uses. Reason? Mike Decided to follow the data sheet and
> >NOT use the Hauppauge specifically select IFs.
>
> If you have one of the latest HVR1600's with that analog tuner, does PAL-D work with it without and offset?
>
I don't have a current model HVR-1600 to hand - if I get hold of one, I will
test it.
--
Simon Farnsworth
Software Engineer
ONELAN Limited
http://www.onelan.com/
prev parent reply other threads:[~2011-10-03 8:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 12:50 Problems tuning PAL-D with a Hauppauge HVR-1110 (TDA18271 tuner) - workaround hack included Simon Farnsworth
2011-09-28 14:20 ` Devin Heitmueller
2011-09-28 14:27 ` Simon Farnsworth
2011-09-30 10:48 ` Mauro Carvalho Chehab
2011-09-30 11:03 ` Simon Farnsworth
2011-09-30 11:59 ` Mauro Carvalho Chehab
2011-09-30 14:43 ` Devin Heitmueller
2011-09-30 11:11 ` Simon Farnsworth
2011-09-30 13:35 ` Mauro Carvalho Chehab
2011-09-30 18:05 ` Malcolm Priestley
2011-10-03 8:56 ` Simon Farnsworth
2011-09-30 19:37 ` Steven Toth
2011-09-30 21:25 ` Andy Walls
2011-10-03 8:57 ` 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=201110030957.58627.simon.farnsworth@onelan.com \
--to=simon.farnsworth@onelan.com \
--cc=awalls@md.metrocast.net \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@infradead.org \
--cc=mkrufky@kernellabs.com \
--cc=stoth@kernellabs.com \
/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.