From: David Henningsson <david.henningsson@canonical.com>
To: Clemens Ladisch <clemens@ladisch.de>
Cc: Chase Douglas <chase.douglas@canonical.com>,
alsa-devel@alsa-project.org,
David Woodhouse <david.woodhouse@intel.com>
Subject: Re: Merging alsa-firmware into linux-firmware
Date: Wed, 21 Jul 2010 15:31:26 +0200 [thread overview]
Message-ID: <4C46F6AE.3060208@canonical.com> (raw)
In-Reply-To: <4C469959.7020600@ladisch.de>
On 2010-07-21 08:53, Clemens Ladisch wrote:
> 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.
Right. I'll leave them out for now (i e I'll not merge them) for the
following reasons:
1) The people having these files could just put them in /lib/firmware
instead of in /etc/sound
2) The symlinks never worked on Medibuntu, and Medibuntu got no bugs
about that, so probably noone out there uses the firmware anyway. ;-)
>>> (Er, wasn't there a regression introduced in the emi62 firmware in
>>> 2.6.27?)
> http://xiphmont.livejournal.com/46858.html
The emi26/emi62 firmware already exists in linux-firmware, so I won't
merge them either (and that patch in the link is against linux-firmware
and not alsa-firmware).
--
David Henningsson, Canonical Ltd.
http://launchpad.net/~diwic
next prev parent reply other threads:[~2010-07-21 13:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-20 10:38 Merging alsa-firmware into linux-firmware David Henningsson
2010-07-20 10:51 ` David Woodhouse
2010-07-21 9:29 ` David Henningsson
2010-07-21 9:31 ` David Woodhouse
2010-07-26 8:15 ` David Henningsson
2010-07-26 8:36 ` Takashi Iwai
2010-07-20 13:31 ` Clemens Ladisch
2010-07-20 15:47 ` David Henningsson
2010-07-21 6:53 ` Clemens Ladisch
2010-07-21 13:31 ` David Henningsson [this message]
2010-07-21 14:02 ` David Woodhouse
2010-07-21 14:30 ` David Henningsson
2010-07-20 13:36 ` Takashi Iwai
2010-07-22 10:07 ` David Henningsson
2010-07-22 11:20 ` Takashi Iwai
2010-07-22 12:41 ` David Henningsson
2010-07-22 12:46 ` Takashi Iwai
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=4C46F6AE.3060208@canonical.com \
--to=david.henningsson@canonical.com \
--cc=alsa-devel@alsa-project.org \
--cc=chase.douglas@canonical.com \
--cc=clemens@ladisch.de \
--cc=david.woodhouse@intel.com \
/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