hp at bitrange
Feb 16, 2003, 8:52 PM
Post #1 of 3
(1024 views)
Permalink
|
|
New firmware extractor finally committed
|
|
Right, an updated version of the one I sent in 10 days ago :-/
called ivtvfwextract.
The main difference to that version is that I made it default
compatible with the current fw load scheme (the clunky
two-files-each-128k each for decoder and encoder). The fw is
extracted as /lib/modules/ivtv-enc-fw-1.bin, -2.bin and
ivtv-dec-fw-1.bin, -2.bin by default. See the updated
utils/README.
If you want to change these paths, no worries, but please choose
an expected kernel-ish system location as with other firmware.
Search the kernel for clues.
I took the liberty to change ivtv.h to match these names, so
things stand a chance to work out of the box. I think
"/home/tmk/src" does not, unless you're Kevin. ;-)
I also removed utils/bin-asc.c and extract-fw.c to avoid
confusion. For those new to CVS: don't worry, they're still
there, but now kept in the Attic.
There's an option --use-encoder-image=N (N=1,2) required (only)
for those wacky updated drivers that contains multiple *encoder*
images. (I think I wrote *decoder* images in that earlier
message: my fault.) I still don't know which one to use for
what occasion, so please share your findings. Maybe we can even
ask Hauppauge now.
If you've already extracted the firmware, then you're fine and
you can ignore this message, except you may want to move your
firmware to match the expected location in ivtv.h.
Bug reports to me. I'll try to be quicker with fixes than with
decoder development...
brgds, H-P
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
ivtv-devel mailing list
ivtv-devel [at] lists
https://lists.sourceforge.net/lists/listinfo/ivtv-devel
|
