Subject: Re: non-free firmware in kernel modules, aggregation and unclear
	copyright notice.
From: Josselin Mouette <joss@debian.org>
To: linux-os@analogic.com
Cc: debian-kernel@lists.debian.org, debian-legal@lists.debian.org,
       linux-kernel@vger.kernel.org, linux-acenic@sunsite.dk
In-Reply-To: <Pine.LNX.4.61.0504070855510.29251@chaos.analogic.com>
References: <L0f93D.A.68G.D2OVCB@murphy> <4255278E.4000303@almg.gov.br>
	 <Pine.LNX.4.61.0504070855510.29251@chaos.analogic.com>
Content-Type: text/plain; charset=ISO-8859-15
Date: Thu, 07 Apr 2005 16:15:45 +0200
Message-Id: <1112883345.6421.42.camel@silicium.ccc.cea.fr>
Mime-Version: 1.0
Content-Transfer-Encoding: 8BIT
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1138
Lines: 25

Le jeudi 07 avril 2005 ? 09:03 -0400, Richard B. Johnson a ?crit :
> Well it doesn't make any difference. If GPL has degenerated to
> where one can't upload microcode to a device as part of its
> initialization, without having the "source" that generated that
> microcode, we are in a lot of hurt. Intel isn't going to give their
> designs away.

The GPL doesn't forbid that. The GPL forbids to put this microcode
directly in the same binary as the GPL code. Of course, nothing forbids
some GPL'ed code to take a binary elsewhere and to upload it into the
hardware.

At least that's my opinion; AIUI, Sven Luther believes it is possible if
the firmware has a decent (but not necessarily free) license.
-- 
 .''`.           Josselin Mouette        /\./\
: :' :           josselin.mouette@ens-lyon.org
`. `'                        joss@debian.org
   `-  Debian GNU/Linux -- The power of freedom

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/