From: Adam Glover <aglover.v4l@mindspring.com>
To: video4linux-list@redhat.com
Subject: odd behavior in tuner module in hg and linux stable
Date: Wed, 7 May 2008 23:51:16 -0700 (GMT-07:00) [thread overview]
Message-ID: <5143530.1210229476468.JavaMail.root@mswamui-thinleaf.atl.sa.earthlink.net> (raw)
This has to do with the patch I submitted to add explicit
support for the ADS Tech Instant HDTV PCI card (PTV-380).
It appears that in the latest kernel stable release as well
as the hg snapshot I had used for the patch the tuner module
does not identify the tuner chip on its initial automatic
loadup. I must rmmod and reinsert the tuner module before it
will report detecting the TDA9887 / TUV1236D tuner chips.
This did not happen with version 2.6.24.4 so I'm wondering
what changed? As it stands, it's not fatal to have to remove
and reinsert the module but it's not right...
This seems to be change from the last couple of months that
has already made it into the stable kernel tree.
Incidentally, the dvb frontend loads and works despite the
tuner having not registered the chips. I just have no control
over analog tuning. I don't know if this is normal behavior
or not.
So is this some sort of bug or is there something I should
do with the card config when compiling the modules?
I'd like to see the card working (even though I have a pcHDTV
card coming in the mail...)
Adam Glover
(I do apologize if I did not submit that patch correctly...
I'm pretty sure I was wrong in not including relative paths
and that the patch had to be run inside the saa7134 folder...)
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next reply other threads:[~2008-05-08 6:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-08 6:51 Adam Glover [this message]
2008-05-08 21:54 ` odd behavior in tuner module in hg and linux stable Hartmut Hackmann
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=5143530.1210229476468.JavaMail.root@mswamui-thinleaf.atl.sa.earthlink.net \
--to=aglover.v4l@mindspring.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