linux-kernel - Re: GPL vs non-GPL device drivers

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Message-ID: <9b3a62ab0702151800r3fdb6d64offc6e1de5837b4fd@mail.gmail.com>
Date:	Thu, 15 Feb 2007 18:00:36 -0800
From:	"v j" <vj.linux@...il.com>
To:	"Scott Preece" <sepreece@...il.com>, linux-kernel@...r.kernel.org
Subject: Re: GPL vs non-GPL device drivers

On 2/15/07, Scott Preece <sepreece@...il.com> wrote:
> On 2/15/07, v j <vj.linux@...il.com> wrote:
> > So far I have heard nothing but, "if you don't contribute, screw you."
> > All this is fine. Just say so. Make it black and white. Make it
> > perfectly clear what is and isn't legal. If we can't load proprietary
> > modules, then so be it. It will help everybody if this is out in the
> > clear, instead of resorting to stupid half measures like
> > EXPORT_SYMBOL_GPL.
> ---
>
> I'm not sure what you're asking for. Greg KH's statement was pretty
> black-and-white, and there are a lot of comments in this stream, from
> name-brand developers, that are in line with them. They're the best
> answer you can hope for on this question. The question you're asking
> is an issue of interpretation, which only a court can answer. Do you
> want them to modify the license to make this particular issue clearer?
> Or do you just want a statement from Linus?

Which statement are you talking about? First of all it is not clear to
me if proprietary modules need to be GPL or not. If they do, I guess I
have nothing to say. If that is the way developers want it, so be it.

Assuming these need not be GPL, I have a problem with
EXPORT_SYMBOL_GPL and the general trend in the direction of making
proprietary drivers harder on companies. Our drivers use basic
interfaces in the kernel like open, read, write, ioctl, semaphores,
interrupts, timers etc. This is functionality we would expect from any
operating system. We used devfs before and had no problems there. Greg
KH has gone and made the basic sysfs interface, which any generic
driver could use as EXPORT_SYMBOL_GPL. I don't really care, I just
don't use sysfs. The point is that old functionality is being ripped
off and new ones introduced, and their interfaces are not open
anymore. Hence there will be a point where non-GPLed drivers simply
cannot be loaded.

So why beat about the bush? Just make it illegal to load proprietary
drivers, or remove EXPORT_SYMBOL_GPL.

vj.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/