From alsa-devel-owner@alsa.jcu.cz  Mon Mar  8 04:39:38 1999
Received: from cyphyn.219.org (nwhn-sh7-port20.snet.net [204.60.16.20])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id EAA10033
	for <alsa-devel@alsa.jcu.cz>; Mon, 8 Mar 1999 04:39:20 +0100
Received: from localhost (ffloberg@localhost)
          by cyphyn.219.org (8.8.4/8.8.4) with ESMTP
	  id WAA00834 for <alsa-devel@alsa.jcu.cz>; Sun, 7 Mar 1999 22:30:04 -0500
Date: Sun, 7 Mar 1999 22:30:04 -0500 (EST)
From: Fred Floberg <ffloberg@snet.net>
To: alsa-devel@alsa.jcu.cz
Subject: Re: ALSA Soundcard Vendor Information
In-Reply-To: <19990307202853.G22312@ruhr-uni-bochum.de>
Message-ID: <Pine.LNX.4.05.9903072221420.745-100000@cyphyn.219.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: alsa-devel@alsa.jcu.cz
Sender: alsa-devel-owner@alsa.jcu.cz
Precedence: list




On Sun, 7 Mar 1999, Marcus Brinkmann wrote:

> Note that if you include Firmware in the Alsa distribution, it will be
> difficult for me to comply to the GPL when distributing ALsa, because I
> can't copy the source of the firmware, as the GPL requests. So non-free
> Firmware should probably be distributed and made available outside of Alsa.

Is firmware usually distributed as a seperate file on the installation
floppies/cdroms that come with the hardware?

If so then it doesn't seem like too much of a problem to have owners of
the hardware copy the firmware from the installation disk into
/usr/lib/something_or_other/ and have ALSA upload it to the card from there.

Does that make sense to do? I've never owned a card that needed to have its
firmware uploaded on boot-up.


Fred



