From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 25 May 2001 07:14:30 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 25 May 2001 07:14:19 -0400 Received: from router-100M.swansea.linux.org.uk ([194.168.151.17]:4365 "EHLO the-village.bc.nu") by vger.kernel.org with ESMTP id ; Fri, 25 May 2001 07:14:04 -0400 Subject: Re: Fwd: Copyright infringement in linux/drivers/usb/serial/keyspan*fw.h To: johnc@damncats.org (John Cavan) Date: Fri, 25 May 2001 12:10:31 +0100 (BST) Cc: aaronl@vitelus.com (Aaron Lehmann), linux-kernel@vger.kernel.org (Linux Kernel) In-Reply-To: <3B0E2D3B.EDC082A6@damncats.org> from "John Cavan" at May 25, 2001 06:00:27 AM X-Mailer: ELM [version 2.5 PL3] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: From: Alan Cox Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > Not to sound dense, but what part of the GPL prohibits a piece of GPL'd > software from including non-GPL'd code? The GPL does explicitly state > that you can't include it's software in proprietary code, but I don't > recall seeing a provision that prohibits the other way around. The same thinbg holds true both ways. A work containing GPL code must be GPL or freer. Adding either to the other is the same thing. The firmware is a seperate work, and its mere aggregation even if a .o file is a more unusual archive formt