From: Bob Cunningham <rcunning@acm.org>
To: linux-media@vger.kernel.org
Subject: HVR-950Q problem under MythTV
Date: Wed, 28 Oct 2009 19:10:38 -0700 [thread overview]
Message-ID: <4AE8F99E.5010701@acm.org> (raw)
I just completed a fresh install of MythTV 0.22 RC1 on my fully-updated Fedora 11 system. My tuner is an HVR-950Q, connected to cable. The tuner works fine under tvtime (SD) and xine (HD).
All MythTV functions work, except LiveTV. The problem is that mythfrontend times out waiting for the HVR-950Q to tune to the first station. This appears to be due to the very long HVR-950Q firmware load time, since no errors are reported by the backend.
Unfortunately, mythfrontend has a hard-wired 7 second timeout for most requests sent to the backend. It seems this timeout works fine under normal circumstances for every other tuner MythTV works with.
The following is repeated in dmesg after every attempt:
xc5000: waiting for firmware upload (dvb-fe-xc5000-1.6.114.fw)...
usb 1-2: firmware: requesting dvb-fe-xc5000-1.6.114.fw
xc5000: firmware read 12401 bytes.
xc5000: firmware uploading...
xc5000: firmware upload complete...
It looks like the HVR-950Q driver reloads the firmware at every possible opportunity, independent of the hardware state, each time either the SD or HD device is opened, such as when changing from an SD channel on /dev/video0 to an HD channel on /dev/dvb/adapter0. Is this necessary?
Is it possible to tell the driver to ease up on the firmware reloads? I don't mind if the first attempt fails, but the second attempt should succeed (without a reload).
Alternatively, are faster firmware loads possible?
Should I open a bug on this?
next reply other threads:[~2009-10-29 2:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-29 2:10 Bob Cunningham [this message]
2009-10-29 3:40 ` HVR-950Q problem under MythTV Devin Heitmueller
2009-10-29 4:47 ` Bob Cunningham
2009-10-29 4:56 ` Devin Heitmueller
2009-10-29 5:33 ` Bob Cunningham
2009-10-29 12:59 ` Devin Heitmueller
2009-10-29 13:38 ` Bob Cunningham
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=4AE8F99E.5010701@acm.org \
--to=rcunning@acm.org \
--cc=linux-media@vger.kernel.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