lkml.org 
[lkml]   [2006]   [May]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
SubjectRE: GPL and NON GPL version modules
Date
From
Hi Jan,

So, if the proprietary code exposes an interface and if the code within
the GPL makes a call to that interface, will the proprietary code become
part of GPL. Please suggest

Regards,
Nutan

-----Original Message-----
From: Jan Engelhardt [mailto:jengelh@linux01.gwdg.de]
Sent: Monday, May 15, 2006 5:39 PM
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

>
>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/

\
 
 \ /
  Last update: 2006-05-15 14:15    [W:0.076 / U:0.172 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site