All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Toth <stoth@kernellabs.com>
To: Simon Farnsworth <simon.farnsworth@onelan.com>
Cc: 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: Fri, 30 Sep 2011 15:37:30 -0400	[thread overview]
Message-ID: <CALzAhNW3DGtMqqhWiC2WwYiw5a4D5bc7B-P5g8mkKmGOfV1QRg@mail.gmail.com> (raw)
In-Reply-To: <201109281350.52099.simon.farnsworth@onelan.com>

>                map = &std_map->atv_dk;

Simon,

I've been chewing on this for a day or so and it reminded me partly
why I stopped working on combined PAL/NTSC support for the saa7164
hardware family, it's been bugging me for a reason - now I understand
why.

Essentially, I had a long discussion with Mike Krufky about a year ago
related to I/F's for analog TV output. The SAA7164 analog demod IF (as
best as I can tell) are not configurable. I have no good set_if()
interface I can call on the tuner to select a different I/F as the
bridge driver needs. I was fairly unhappy about that..... bah, such is
life.

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.

His advise to me, at the time, which I think will work nicely for you
and probably a better patch, is to have the HVR-1110 define a better
I/F map for the atv_dk case. This way at least you would not pollute
the 18271 driver in it's core and effect other DK users (potentially),
instead, for the HVR1110 18271 attach, define the I/F maps for each
country/modulation and simple change the DK version by your desired
offset.

That may be a cleaner fix and accepted for merge.

(Note to self: Now that I recall the conversation with Mike I may
actually go ahead and fix my saa7164 Pal issue.)

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

  parent reply	other threads:[~2011-09-30 19:37 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 [this message]
2011-09-30 21:25   ` Andy Walls
2011-10-03  8:57     ` Simon Farnsworth

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=CALzAhNW3DGtMqqhWiC2WwYiw5a4D5bc7B-P5g8mkKmGOfV1QRg@mail.gmail.com \
    --to=stoth@kernellabs.com \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@infradead.org \
    --cc=mkrufky@kernellabs.com \
    --cc=simon.farnsworth@onelan.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.