Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261151AbUKESwF (ORCPT ); Fri, 5 Nov 2004 13:52:05 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261157AbUKESwF (ORCPT ); Fri, 5 Nov 2004 13:52:05 -0500 Received: from sanosuke.troilus.org ([66.92.173.88]:9101 "EHLO sanosuke.troilus.org") by vger.kernel.org with ESMTP id S261151AbUKESwA (ORCPT ); Fri, 5 Nov 2004 13:52:00 -0500 To: "Adam J. Richter" Cc: davids@webmaster.com, jp@enix.org, linux-kernel@vger.kernel.org Subject: Re: Possible GPL infringement in Broadcom-based routers References: <200411061040.iA6AeZp03452@freya.yggdrasil.com> From: Michael Poole Date: 05 Nov 2004 13:51:57 -0500 In-Reply-To: <200411061040.iA6AeZp03452@freya.yggdrasil.com> Message-ID: <87oeicuo1e.fsf@sanosuke.troilus.org> User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1151 Lines: 18 Adam J. Richter writes: > I think you're missing the idea that that such drivers are > _contributory_ infringement to the direct infringement that occurs when > the user loads the module. In other words, even for a driver that has > not a byte of code derived from the kernel, if all its uses involve it > being loaded into a GPL'ed kernel to form an infringing derivative > work in RAM by the user committing direct copyright infringement against > numerous GPL'ed kernel components, then it fails the test of having > a substantial non-infringing use, as established in the Betamax decision, > and distributing it is contributory infringement of those GPL'ed > components of the kernel. Combining GPLed works with GPL-incompatible works violates the GPL if you distribute the result; the GPL allows one to make that kind of combination for one's own use. Go read the GPL more closely. Michael Poole - 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/