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: <20070225193907.GA1802@elf.ucw.cz>
Date:	Sun, 25 Feb 2007 20:39:07 +0100
From:	Pavel Machek <pavel@....cz>
To:	David Schwartz <davids@...master.com>
Cc:	"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: Re: GPL vs non-GPL device drivers

On Sun 2007-02-25 03:33:38, David Schwartz wrote:
> 
> > But... how does situation change when Evil Linker does #include
> > <pop3/gpl_header_file_with_some_inline_functions.h> from his
> > binary-only part?
> 
> Right, but *why* is he doing that? The answer: It is the most practical way
> to write his driver.

Most practical way to get something Windows compatible is to pirate
Windows; I do not think that gives me permission to do so.

Similary, there are many ways to write inline functions present in
headers, and no, embedded developer being lazy does not mean they can
copy those functions into their proprietary module.
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
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/