From: Vanessa Ezekowitz <vanessaezekowitz@gmail.com>
To: video4linux-list@redhat.com
Subject: Re: KWorld ATSC 110 and NTSC [was: 2.6.25+ and KWorld ATSC 110 inputs]
Date: Sun, 30 Nov 2008 20:47:41 -0600 [thread overview]
Message-ID: <200811302047.41466.vanessaezekowitz@gmail.com> (raw)
In-Reply-To: <493340A6.5050308@rogers.com>
On Sunday 30 November 2008 07:40:54 pm CityK wrote:
> stuart wrote:
> > V4L support for the KWorld ATSC120 is limited. There a numerous threads
> > here which talk about the problems and some work arounds. The
> > developers have talked about adding support but consider new features at
> > the cost of an overhaul of the current driver.
> >
> > Right now I believe you can not use both ATSC and NTSC tuners w/o power
> > cycling your computer and bringing it up with (only) the appropriate
> > driver. Also, I don't believe the IR receiver works under V4L. This
> > card replaced the Kworld 110 and Kworld 115 tuners. If you can find
> > these older Kworld ATSC tuners, I would buy them instead as I believe
> > they are better supported under V4L (I also have a Kworld ATSC110 - but
> > only use it for ATSC tuning as well).
> > Go here and read up on how people are setting this card up:
> > > http://www.linuxtv.org/wiki/index.php/KWorld_ATSC_120
> >
> > I'm using the Kworld 120 as an ATSC tuner and nothing else in a Debian
> > mythtv slave back end system.
The OP was talking about the older 110 to begin with...so he already has one ;)
On my setup, with an ATSC 120 (not the 110), power cycling or rebooting is still necessary to switch between analog/NTSC and digital/ATSC modes. Trying to load both DVB and V4L drivers either renders the card inoperable, or one or the other mode simply won't work.
In my case, for example, loading the analog driver (modprobe cx8800) followed by the DVB drivers (modprobe cx88-dvb) results in working analog mode, but digital mode is defunct. Rebooting and loading either of the two alone results in that mode working fine indefinitely.
Has there been a change to the driver that I'm not aware of? I'm curious...
--
"There are some things in life worth obsessing over. Most
things aren't, and when you learn that, life improves."
Vanessa Ezekowitz <vanessaezekowitz@gmail.com>
--
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 2:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-01 1:40 KWorld ATSC 110 and NTSC [was: 2.6.25+ and KWorld ATSC 110 inputs] CityK
2008-12-01 2:47 ` Vanessa Ezekowitz [this message]
2008-12-01 3:18 ` CityK
-- strict thread matches above, loose matches on Subject: below --
2008-12-01 2:09 CityK
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 19:55 ` stuart
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=200811302047.41466.vanessaezekowitz@gmail.com \
--to=vanessaezekowitz@gmail.com \
--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