Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932329AbWEOMIu (ORCPT ); Mon, 15 May 2006 08:08:50 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751444AbWEOMIu (ORCPT ); Mon, 15 May 2006 08:08:50 -0400 Received: from linux01.gwdg.de ([134.76.13.21]:8408 "EHLO linux01.gwdg.de") by vger.kernel.org with ESMTP id S1751417AbWEOMIt (ORCPT ); Mon, 15 May 2006 08:08:49 -0400 Date: Mon, 15 May 2006 14:08:35 +0200 (MEST) From: Jan Engelhardt To: "Srinivas G." cc: linux-kernel-Mailing-list , Fawad Lateef , jjoy@novell.com, "Nutan C." , "Mukund JB." , gauravd.chd@gmail.com, bulb@ucw.cz, greg@kroah.com, Shakthi Kannan Subject: Re: GPL and NON GPL version modules In-Reply-To: Message-ID: References: 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: 833 Lines: 26 > >If I have a module called module A which uses the GPL code and module B >uses the NON GPL (proprietary) code. If the module A depends on module >B, is it possible to load these modules? > Technically yes. >Will it be violating any GPL Rules? > [ big IANAL sticker ] More or less. If my understanding of the GPL is correct, the "combined" thing (the kernel machinery, as in: the contents of your RAM) becomes GPL. But since proprietary code involved, it's gets a hell lot more complicated, since, obviously, you can't just GPLize proprietary code of others. Jan Engelhardt -- - 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/