From: Mark Lord <lkml@rtr.ca>
To: Devin Heitmueller <dheitmueller@kernellabs.com>
Cc: Steven Toth <stoth@linuxtv.org>,
linux-media@vger.kernel.org,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Regression 2.6.31: xc5000 no longer works with Myth-0.21-fixes branch
Date: Sun, 19 Jul 2009 11:53:18 -0400 [thread overview]
Message-ID: <4A63416E.2070103@rtr.ca> (raw)
In-Reply-To: <4A6337C1.6080104@rtr.ca>
Mark Lord wrote:
..
> Really, the mythfrontend DOES NOT DEAL WITH TUNERS directly,
> leaving that to the mythbackend. EXCEPT for when it wants to show
> a signal strength/quality indication onscreen, which is done
> when tuning to a new channel.
>
> So it's got to be something on that pathway, I suspect,
> but despite being a kernel developer, I'm not terribly
> knowledgeable about V4L, DVB, or the MythTV internals.
..
Okay, got it. Sort of. :)
1. Patched mythtv to not show the signal strength info. No effect.
2. Substituted a different brand/model/chipset DVB tuner for the 950Q,
and everything was working fine again. So we know it's not a generic issue.
3. In mythtv-setup -> CaptureCards -> DVB:1 -> RecordingOptions
there is a tickbox for "Open DVB Card on Demand". It was ticked,
so I un-ticked that box. Everything now works!
When that tickbox was selected, the xc5000 took five (5) seconds to "open",
as it did the firmware upload every time. This appeared to exceed some
timeout inside myth.
With the tickbox NOT ticked, myth just opens the tuner once at startup,
and keeps it open, so no more delay when it wants to use it.
I wonder if we can be smarter/faster about the xc5000 firmware uploads?
Cheers
next prev parent reply other threads:[~2009-07-19 15:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-19 13:15 Regression 2.6.31: xc5000 no longer works with Myth-0.21-fixes branch Mark Lord
2009-07-19 14:06 ` Devin Heitmueller
2009-07-19 14:45 ` Mark Lord
2009-07-19 18:25 ` Mark Lord
2009-07-19 15:12 ` Mark Lord
2009-07-19 15:53 ` Mark Lord [this message]
2009-07-19 22:42 ` Mark Lord
2009-07-20 1:12 ` Devin Heitmueller
2009-07-20 1:57 ` Mark Lord
2009-07-20 1:59 ` Devin Heitmueller
2009-07-21 2:38 ` Mark Lord
2009-07-20 2:18 ` Mark Lord
2009-07-20 2:32 ` 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=4A63416E.2070103@rtr.ca \
--to=lkml@rtr.ca \
--cc=dheitmueller@kernellabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=stoth@linuxtv.org \
/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