[lkml]   [2001]   [Oct]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: Module Licensing?
On Wed, 31 Oct 2001, Timur Tabi wrote:

> The fact that the open source portions and the closed source portions
> can't function on their own is irrelevant, IMHO.
> Please show me where in the GPL text it says that the act of compiling a
> module and loading it into memory is subject to the GPL.

That'd be paragraph 2 b)

b) You must cause any work that you distribute or publish, that in
whole or in part contains or is derived from the Program or any
part thereof, to be licensed as a whole at no charge to all third
parties under the terms of this License.

... These requirements apply to the modified work as a whole.

Since your program, which happens to consist of one open
source part and one proprietary part, is partly a derived
work from the kernel source (by using kernel header files
and the inline functions in it) your whole work must be
distributed under the GPL.

> > If you wanted to provide a mixed source/binary driver that wasnt derivative
> > of the kernel (and there are lots of reasons for it) - don't GPL your
> > open source bit use something like MPL or BSD
> Our open source bits are GPL because they are "derived" from the kernel
> source, which is also GPL.

"open source bits" ... from "the work as a whole" ?


DMCA, SSSCA, W3C? Who cares?

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:12    [W:0.100 / U:0.340 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site