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-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <MDEHLPKNGKAHNMBLJOLKKEIMBKAC.davids@webmaster.com>
Date:	Fri, 16 Feb 2007 18:42:35 -0800
From:	"David Schwartz" <davids@...master.com>
To:	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Cc:	<trent.waddington@...il.com>, "Neil Brown" <neilb@...e.de>
Subject: RE: GPL vs non-GPL device drivers

> On Thu, Feb 15, 2007 at 04:38:41PM -0800, David Schwartz wrote:

> > Just to be perfectly clear, it is an outrageous claim that *every*
> > *possible* kernel module must be a derivative work of the
> > kernel. Copyright
> > *cannot* protect every possible way to accomplish a particular
> > function (and
> > "a Linux driver for the X800 graphics chipset" is a function).

> This is just your personal opinion.

Umm, no. It's clearly the law. Again, see Lexmark v. Static Controls, among
other cases.

> "derivative work" is a term with many grey areas.
> Does linking create a derivative work?

I don't think that's grey at all. I think it's perfectly clear that linking
cannot create a derivative work. No automated process can -- it takes
creativity to create a derivative work. (That doesn't mean that just because
you can link A to B, a cannot be a derivative work of B or vice verse, of
course. It just means that if A is not a derivative work of B, linking A to
B cannot make it so, nor can the result be a derivative work.)

> Or including the code of one "static inline" function in your binary?

That would be a tricky border case. I wouldn't presume to be able to predict
the result of an inquiry into a case like that.

> There is no border everyone agrees on.

That's not the issue. The fact that we can't agree on precisely where red
ends and orange begins is not a counter-argument to a claim that a
particular thing is *clearly* red.

> And even judges in different jurisdictions might decide differently
> based on different copyright laws.

Sure, in border cases, but not in cases where it's perfectly clear.

> Perhaps some module would be considered legal in the USA and Russia but
> illegal in Germany and China, or the other way round.

I agree. I am mostly talking about US law.

> > Copyright can
> > *only* protect the one possible way you chose to do something
> > out of a large
> > number of equally good possible ways. (See, for example,
> > Lexmark v. Static
> > Controls where courts held that Static Controls could take Lexmark's TLP
> > software because that was the only practical way to make a
> > compatible toner
> > cartridge.)
> >...

> It's always funny seeing people making univeral claims only based on
> laws and court cases that have zero relevance for > 95% of all people...

I cite the case only because it does a good job of explaining the principle.
Copyright cannot allow you to own every practical way of accomplishing
something. It can only allow you to own the one particular way you chose to
do something out of a universe of other possible equally good ways. Only
patent allows you to protect the "best way" or "every way" to perform a
function.

DS

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