From: David Engel <david@istwok.net>
To: Jason Pontious <jpontious@gmail.com>
Cc: video4linux-list@redhat.com
Subject: Re: Kworld 115-No Analog Channels
Date: Fri, 30 May 2008 12:18:50 -0500 [thread overview]
Message-ID: <20080530171850.GA8130@opus.istwok.net> (raw)
In-Reply-To: <f50b38640805300841q1a4f05c3udbf0d0f7f19cdb6e@mail.gmail.com>
On Fri, May 30, 2008 at 11:41:54AM -0400, Jason Pontious wrote:
> I am using the current v4l-dvb from mercurial as the latest there now has a
> feature to allow you to select the rf input for analog channels which I
> would like to have. I upgraded to 2.6.25 in Ubuntu because of the way
> Ubuntu is currenlty handling their kernel modules doesn't allow for an easy
> compile of the drivers from mercurial.
I was not aware the input selection method had been changed again.
Thanks. Now, I'll know to expect a conflict with my own hack when
this makes it into the mainline kernel.
Note to Michael Krufky. I could be [probably am] missing something,
but to me it looks like there is no way to force the use of input 0
when QAM is used.
case TUNER_PHILIPS_FCV1236D:
{
unsigned int new_rf;
if (dtv_input[priv->nr])
new_rf = dtv_input[priv->nr];
else
switch (params->u.vsb.modulation) {
case QAM_64:
case QAM_256:
new_rf = 1;
break;
case VSB_8:
default:
new_rf = 0;
break;
}
simple_set_rf_input(fe, &buf[2], &buf[3], new_rf);
break;
}
If dtv_input is set to 0, it will be misinterpreted as autoselect and
then the use of QAM_64 or QAM_256 will make the code use input 1!
David
--
David Engel
david@istwok.net
--
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-05-31 16:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-29 22:57 Kworld 115-No Analog Channels Jason Pontious
2008-05-30 14:58 ` David Engel
2008-05-30 15:41 ` Jason Pontious
2008-05-30 17:18 ` David Engel [this message]
2008-06-01 7:15 ` Michael Krufky
2008-06-01 19:07 ` David Engel
2008-06-01 7:18 ` Michael Krufky
2008-06-01 19:03 ` David Engel
2008-06-01 19:10 ` Michael Krufky
2008-06-01 20:46 ` hermann pitton
2008-06-02 20:04 ` Michael Krufky
2008-06-02 20:51 ` Mauro Carvalho Chehab
2008-06-03 0:45 ` hermann pitton
2008-06-01 20:55 ` David Engel
2008-06-02 20:09 ` Michael Krufky
2008-06-03 15:04 ` David Engel
2008-06-04 0:01 ` Jason Pontious
2008-06-04 1:38 ` Michael Krufky
2008-06-11 18:05 ` Jason Pontious
2008-06-01 7:20 ` Michael Krufky
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=20080530171850.GA8130@opus.istwok.net \
--to=david@istwok.net \
--cc=jpontious@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