From: Christopher Pascoe <linuxdvb@itee.uq.edu.au>
To: video4linux-list@redhat.com
Subject: Re: No scan with DViCo FusionHDTV DVB-T Dual Express
Date: Mon, 6 Apr 2009 22:39:44 -0700 [thread overview]
Message-ID: <bfa9a8f30904062239l2d096accj47c1fb8d50eafcf7@mail.gmail.com> (raw)
(Hopefully this email will join the thread - I just joined the list briefly
so I could post.)
I had a few minutes while stuck on a bus and had a look at the code in
v4l-dvb tip. It appears that the driver there has at least two problems -
it resets the wrong (or no) tuner in the callback and it potentially locks
up the I2C bus through tinkering with the zl10353's gate_control logic. The
first alone would cause an "incorrect readback of firmware version" message
after the first tune. The second would explain the device subids
disappearing and your having to use card=11 for the board to be found.
Try the patch at
http://www.itee.uq.edu.au/~chrisp/Linux-DVB/DVICO/dual-digital-express-dvb-t-fix-20090407-1.patch.
It probably addresses these two issues (it's not even compile tested,
so
if it doesn't build I'm sure you get the idea) and see if it makes any
difference.
Regards,
Chris
--
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:[~2009-04-07 5:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-07 5:39 Christopher Pascoe [this message]
2009-04-22 16:58 ` No scan with DViCo FusionHDTV DVB-T Dual Express Devin Heitmueller
-- strict thread matches above, loose matches on Subject: below --
2009-03-31 12:22 john knops
2009-03-31 14:24 ` Steven Toth
2009-03-31 14:32 ` Devin Heitmueller
2009-04-01 5:39 ` john knops
2009-04-03 13:22 ` john knops
2009-04-06 14:01 ` Steven Toth
2009-04-06 14:16 ` Devin Heitmueller
2009-04-07 13:08 ` john knops
2009-04-07 14:03 ` Devin Heitmueller
2009-04-09 22:23 ` john knops
2009-04-10 22:26 ` Devin Heitmueller
2009-04-11 12:37 ` Steven Toth
2009-04-11 12:39 ` Devin Heitmueller
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=bfa9a8f30904062239l2d096accj47c1fb8d50eafcf7@mail.gmail.com \
--to=linuxdvb@itee.uq.edu.au \
--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 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.