Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266493AbUFQNwG (ORCPT ); Thu, 17 Jun 2004 09:52:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266499AbUFQNwG (ORCPT ); Thu, 17 Jun 2004 09:52:06 -0400 Received: from kinesis.swishmail.com ([209.10.110.86]:17166 "EHLO kinesis.swishmail.com") by vger.kernel.org with ESMTP id S266493AbUFQNvq (ORCPT ); Thu, 17 Jun 2004 09:51:46 -0400 Message-ID: <40D1A606.7000701@techsource.com> Date: Thu, 17 Jun 2004 10:09:10 -0400 From: Timothy Miller MIME-Version: 1.0 To: davids@webmaster.com CC: oliver@neukum.org, erikharrison@gmail.com, linux-kernel@vger.kernel.org Subject: Re: more files with licenses that aren't GPL-compatible References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1000 Lines: 28 David Schwartz wrote: > First, this says, "any work", it's not limited to code. It says, "in whole > or in part contains or is derived from the Program" -- a binary of the Linux > kernel is clearly derived from the Linux kernel source. And it says > "licensed *as a whole* ... under the terms of *this* license". > Ok, so this means that the given binary table which represents the firmware is forced to be under a GPL license. Let's also say, for the circumstances, that what amounts to a hex dump is the "preferred form" of the firmware. Does that make everyone happy? Then get the vendor the say that "the binary form of the firmware" can be converted to GPL as necessary. Now, this may open them up to reverse engineering, but so what. - 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/