From: Bill Pringlemeir <bpringle@sympatico.ca>
To: CityK <cityk@rogers.com>
Cc: V4L <video4linux-list@redhat.com>,
Michael Krufky <mkrufky@linuxtv.org>,
Mauro Carvalho Chehab <mchehab@infradead.org>
Subject: Re: KWorld ATSC 110 and NTSC
Date: Mon, 01 Dec 2008 02:29:10 -0500 [thread overview]
Message-ID: <87k5akbbg9.fsf@sympatico.ca> (raw)
In-Reply-To: <49334769.8070908@rogers.com> (cityk@rogers.com's message of "Sun, 30 Nov 2008 21:09:45 -0500")
On 30 Nov 2008, cityk@rogers.com wrote:
> Bill Pringlemeir wrote:
>> I have experimented with this a bit further. Here are some of my
>> observations,
>> I switch the antenna feed between top and bottom inputs with no effect
>> on getting the NTSC signal.
> The NTSC issue is a known problem.
http://marc.info/?l=linux-video&m=121210186625441&w=2
[... blah blah blah ...]
I did investigate some of the difference between 2.6.24 and more
recent kernels. The code is far better; user should expect some pain.
I was just hoping I was helping with a new issue; but I guess the
kernel lags behind mecurial.
> I tracked the error down to a commit Mauro had made (IIRC, back in
> April) which ended up causing a regression on some boards (e.g. KWorld
> ATSC 110/115). M.Krufky spun a quick patch (which works fine), but it
> cannot be applied to the main Hg sources as it too would break other
> things, and so some discussion would be needed to resolve the underlying
> problem. I was going to bug Mauro about the issue, but never got around
> to it, and I don't know if Mike discussed this with Mauro at the recent
> Plummers conference. (I have cc'ed both in on the message).
> Several posters on AVS forums were complaining of this and I posted a
> link to Mike's patch and instructions (including a warning that it could
> break support with other cards). AFAIK, zero feedback was achieved from
> that, as posters were either too scared by the warning or couldn't
> follow the instructions, nor responded to further posts. Whatever.
Google was not helpful at showing me this thread. I patch and used
'rmmod tuner; modprobe tuner'. This allow NTSC reception.
> In any regard, Mike's patch, as I said, works fine, albeit is not a
> perfect solution as it requires some manual intervention (or script) on
> the part of the user to enable the analogue TV functionality.
> Mauro -- the exact changeset in question is: 7753:67faa17a5bcb
> Mike's patch is located at:
> http://linuxtv.org/~mkrufky/fix-broken-atsc110-analog.patch
No, having an i2c driver muck with a tuner is not nice (it is what was
in the 2.6.24 kernel).
Couldn't the nxt200x driver be placing outputs in OC state via a
'hw_init' and 'hw_fini' type callback (or maybe
hw_quiescent). Switching between analog and digital demodulators would
need something like this? When tuner-simple switches A/D, it needs to
make a call up to the main saa7134 driver to ask for the demodulators
(nxt200x) to be put in the right state (or is the saa7134 already
aware of this switch?). At least, that is what somebody who knows
nothing about this code would expect.
Thanks,
Bill Pringlemeir.
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-12-01 6:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 2:09 KWorld ATSC 110 and NTSC [was: 2.6.25+ and KWorld ATSC 110 inputs] CityK
2008-12-01 7:29 ` Bill Pringlemeir [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-11-26 6:51 2.6.25+ and KWorld ATSC 110 inputs Bill Pringlemeir
2008-11-30 20:15 ` KWorld ATSC 110 and NTSC [was: 2.6.25+ and KWorld ATSC 110 inputs] Bill Pringlemeir
2008-11-30 20:40 ` KWorld ATSC 110 and NTSC Bill Pringlemeir
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=87k5akbbg9.fsf@sympatico.ca \
--to=bpringle@sympatico.ca \
--cc=cityk@rogers.com \
--cc=mchehab@infradead.org \
--cc=mkrufky@linuxtv.org \
--cc=video4linux-list@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox