From: Benjamin Larsson <benjamin@southpole.se>
To: linux-media@vger.kernel.org
Subject: Hauppauge HVR-930C
Date: Wed, 25 Jan 2012 13:06:30 +0100 [thread overview]
Message-ID: <4F1FF046.9050401@southpole.se> (raw)
I tried a daily snapshot (2011-01-24) with this stick. And I'm getting
these kind of errors in the log:
[43665.769571] drxk: SCU_RESULT_INVPAR while sending cmd 0x0203 with params:
[43665.769857] drxk: 02 00 00 00 10 00 07 00 03 02
..........
[43686.121576] drxk: SCU_RESULT_INVPAR while sending cmd 0x0203 with params:
[43686.121861] drxk: 02 00 00 00 10 00 05 00 03 02
..........
[43706.465578] drxk: SCU_RESULT_INVPAR while sending cmd 0x0203 with params:
[43706.465861] drxk: 02 00 00 00 10 00 05 00 03 02
..........
[43709.669571] drxk: SCU_RESULT_INVPAR while sending cmd 0x0203 with params:
[43709.669850] drxk: 02 00 00 00 10 00 05 00 03 02
..........
First I tried the driver with the firmware that is downloaded with the
get_firmware script. The adapter and frontends was registered properly
but I did not get any TS from the stick. I then renamed the firmware
file and the driver complained about missing firmware but stick started
working anyway. So the drxk in my version of the card has a rom with
microcode in it.
So things that would be nice to have is:
A log output that the drxk actually loaded the firmware file. Right now
there is only log output when there is no firmware file detected.
Maybe add a log that the card might work without the drxk firmware.
Silence the SCU_RESULT_INVPAR debug output by default or find out what
is causing the error messages.
MvH
Benjamin Larsson
next reply other threads:[~2012-01-25 12:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 12:06 Benjamin Larsson [this message]
2012-01-25 12:27 ` Hauppauge HVR-930C Mauro Carvalho Chehab
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=4F1FF046.9050401@southpole.se \
--to=benjamin@southpole.se \
--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 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.