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: <Pine.LNX.4.61.0702161019020.4199@chaos.analogic.com>
Date:	Fri, 16 Feb 2007 10:29:53 -0500
From:	"linux-os \(Dick Johnson\)" <linux-os@...logic.com>
To:	"Robert Hancock" <hancockr@...w.ca>
Cc:	"linux-kernel" <linux-kernel@...r.kernel.org>,
	"Manu Abraham" <abraham.manu@...il.com>
Subject: Re: GPL vs non-GPL device drivers

On Thu, 15 Feb 2007, Robert Hancock wrote:

> linux-os (Dick Johnson) wrote:
>> There are a lot of device drivers that will never make it into the
>> mainline kernel because they are for one-of-a-kind devices or boards
>> that companies embed into their products. Nobody would even want a
>> copy of the software to interface with something that they would
>> never even have. When Version 2.6 started, it became necessary to
>> use special tools and procedures to compile a module that was not
>> inside the mainline kernel. However, it was still quite easy. Recently,
>> somebody, apparently with an advanced degree in obfuscation, has made
>> that more difficult. This is abuse, pure and simple. That, in my
>> opinion, is one of the major reasons why people who use Linux in
>> embedded systems end up using very old versions.
>
> What are you talking about? There's nothing wrong with external module
> compilation in current kernels. You need about a 5-line makefile that
> calls the kernel build system, and it works fine.
>
> -- 
> Robert Hancock      Saskatoon, SK, Canada
> To email, remove "nospam" from hancockr@...pamshaw.ca
> Home Page: http://www.roberthancock.com/

Have you tried it recently? Attached is a compressed session
showing 2.6.16.24 compiling fine. Then the same thing is attempted
with 2.6.19. It fails with some "improper configuration" errors.
This script shows that I execute the demanded commands
as 'make oldconfig' and 'make prepare'. Then I try to compile
again resulting, again with the exact same errors.
This was reported on the Linux kernel list and somebody stated,
with much authority BTW, "we don't support out of tree
drivers anymore."

I took that as a clue to create an environment where I don't give
a damn what the obfuscators do anymore. I made some tools that
will allow me to compile my modules. Of course that doesn't fix
the fact that the names and calling parameters of many macros keep
getting changed. I've fixed that by making my own replacements.

>

Cheers,
Dick Johnson
Penguin : Linux version 2.6.16.24 on an i686 machine (5594.84 BogoMips).
New book: http://www.AbominableFirebug.com/
_
..

****************************************************************
The information transmitted in this message is confidential and may be privileged.  Any review, retransmission, dissemination, or other use of this information by persons or entities other than the intended recipient is prohibited.  If you are not the intended recipient, please notify Analogic Corporation immediately - by replying to this message or by sending an email to DeliveryErrors@...logic.com - and destroy all copies of this information, including any attachments, without reading or disclosing them.

Thank you.
Download attachment "typescript.gz" of type "APPLICATION/x-gzip" (42311 bytes)