David Henningsson wrote:
On 2010-07-20 15:31, Clemens Ladisch wrote:
I wonder what you're going to do about the multisound firmware files; the /lib/firmware/turtlebeach/*.bin files are just symbolic links to the actual files in /etc/sound that owners of these cards (if any such still exist) are supposed to have.
Ah, thanks for bringing this up to my attention. From where do these .bin-files come originally?
I don't know more than what Documentation/sound/oss/MultiSound says. The download links in there are, of course, broken; with Google, I've found msndvkit.zip but not pnddk100.zip.
Can we include them?
| This developer's kit does not provide you with a license to distribute | any of the contained software, including, but not limited to | DSPCODE.OBJ, MCONTROL.C. Developers wishing to use these in specific | applications can do so by requesting and returning the "MultiSound DSP | OEM Licensing Agreement". | | Turtle Beach's policy on redistribution is simple. For a license fee | of $1, we allow developers to distribute the above code modules along | with their products, provided that MultiSound hardware is included in | the target product. Since DSP_CODE.OBJ only works with MultiSound | hardware, this is the only logical use of the code.
Try asking Turtle Beach.
(Er, wasn't there a regression introduced in the emi62 firmware in 2.6.27?)
http://xiphmont.livejournal.com/46858.html
Regards, Clemens