lkml.org 
[lkml]   [2001]   [Oct]   [18]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: Non-GPL modules
* Martin Donnelly <md@uklinux.net> on Thu, Oct 18, 2001:

>
> It is a completely naive idea. You export some symbols as
> EXPORT_MODULE_GPL(). I write a wrapper which is GPL'd but i don't export
> my symbols as EXPORT_MODULE_GPL(), i now can interface to your code from
> a proprietry module without breach of license through my wrapper with
> very little work on my part.

Prorprietary modules do that anyways, your workaround isn't anything new
(NVIDIA's module comes to mind). If you don't want to use
EXPORT_MODULE_GPL(), don't use it, and if you're willing to make the effort
to write a wrapper and accept the blight that comes with it, by all means
go ahead. Thanks for pointing out the obvious.

> Your probably the same people who run about using ROT13 as encryption.

I fail to see how this statement has anything to do with the above
paragraph. But anyway, I use PGP-based and other forms of encryption (did
you notice that this e-mail is signed?).

>
> That is you decision and you are free to have it, but don't try and
> force it on other people by saying if you don't have a system running
> 100% GPL'd (or compatibly) licensed kernel - we reserve the right to
> ignore any bugs you try and inform us about, regardless of whether or
> not is is to do with the binary only module. It isn't exactly
> encouraging.
>

It's not force, it's a choice. That taint mechanism is by no means force,
it doesn't force modules to be GPL-compatible, it just taints when a module
isn't. Tainting and EXPORT_MODULE_GPL() are two entirely different things,
intended to accomplish entirely seperate goals. Are you able to make that
distinction? It seems from the posts so far that most people can't. The
only thing in common with tainting and EXPORT_MODULE_GPL() is the
MODULE_LICENSE() macro. Any other comparisons are apples and oranges.

> Perhaps a less blunt tool could be used to encourage people to release
> GPL compatibly licensed code for their previously binary modules? I
> think you risk manufacturers withdrawing the support they have given by
> saying if they don't release their code we won't support anything to do
> with it. Carrots work better than sticks.
>

The GPL was the tool, but since binary-only modules were allowed
EXPORT_MODULE_GPL() takes on that role. And again, you confuse tainting
with GPL-only symbols, the support issue comes from tainted kernels - so
no, we won't support anything to do with unreleased code.

M. R.
[unhandled content-type:application/pgp-signature]
\
 
 \ /
  Last update: 2005-03-22 13:08    [from the cache]
©2003-2011 Jasper Spaans