From: Kevin Wells <wells_kevin@yahoo.co.nz>
To: Jonas Kvinge <linuxtv@closetothewind.net>
Cc: linux-media@vger.kernel.org
Subject: Re: Hauppauge WinTV-HVR-4000 / Nova-HD-S2
Date: Fri, 03 Apr 2009 21:57:32 +1300 [thread overview]
Message-ID: <49D5CF7C.2060704@yahoo.co.nz> (raw)
In-Reply-To: <49D56335.2020506@closetothewind.net>
Jonas Kvinge wrote:
> Whats the command to extract the firmware from the new driver release at
> http://www.wintvcd.co.uk/drivers/88x_2_123_27056_WHQL.zip
>
> The driver at http://www.wintvcd.co.uk/drivers/88x_2_122_26109_WHQL.zip
> is no longer available, so the link on
> http://linuxtv.org/wiki/index.php/Hauppauge_WinTV-HVR-4000 is broken.
>
Hi Jonas,
I can't remember the exact command off the top of my head. But I can
tell you how to work it out.
The problem is how to determine the offset to use. Look at this hex dump
from the start of each firmware file:
dvb-fe-cx24116-1.20.79.0.fw:
00000000 02 11 f9 ec 33 50 03 12
dvb-fe-cx24116-1.22.82.0.fw:
00000000 02 11 fb ec 33 50 03 12
dvb-fe-cx24116-1.23.86.1.fw:
00000000 02 12 02 ec 33 50 03 12
Note the magic `33 50 03 12` bytes that appear at offset 4 in each
firmware file. You can use that to determine the offset of the firmware
in the `hcw88bda.sys` file (at least for the existing firmware files).
I used `hd hcw88bda.sys | more` and typed `/33 50 03 12` in `more` to
find the offset. Make sure to subtract 4 from the offset of the `33 50
03 12` bytes. Convert the offset from hex to decimal and use that as the
`skip` amount for the `dd` command.
Verify the extracted firmware using `md5sum`.
Perhaps when you get it to work you could update the wiki page you
mentioned.
Kevin
next prev parent reply other threads:[~2009-04-03 8:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 1:15 Hauppauge WinTV-HVR-4000 / Nova-HD-S2 Jonas Kvinge
2009-04-03 8:57 ` Kevin Wells [this message]
2009-04-06 13:48 ` Steven Toth
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=49D5CF7C.2060704@yahoo.co.nz \
--to=wells_kevin@yahoo.co.nz \
--cc=linux-media@vger.kernel.org \
--cc=linuxtv@closetothewind.net \
/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