linux-kernel - Re: [ANNOUNCE] Position Statement on Linux Kernel Modules

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: <01ca01c8d715$1b127a60$0125a8c0@wednesday>
Date:	Wed, 25 Jun 2008 15:45:01 -0700
From:	"jdow" <jdow@...thlink.net>
To:	"Willy Tarreau" <w@....eu>, "Matthew" <jackdachef@...il.com>
Cc:	<greg@...ah.com>, "Linux Kernel" <linux-kernel@...r.kernel.org>,
	"Linus Torvalds" <torvalds@...ux-foundation.org>
Subject: Re: [ANNOUNCE] Position Statement on Linux Kernel Modules

From: "Willy Tarreau" <w@....eu>
Sent: Monday, 2008, June 23 06:21


> On Mon, Jun 23, 2008 at 03:02:58PM +0200, Matthew wrote:
>> Hi Greg,
>> 
>> I largely agree to this statement,
>> 
>> there are however some downsides if you're preventing driver
>> manufacturers (e.g. nvidia, ...) from the possibility to offer their
>> customers proprietary drivers:
>> 
>> 1) One big and important point for me (and more and more future
>> linux-users) is powersaving features on GPUs like powermizer (by
>> nvidia) and powerplay (by AMD/ATI) or other hardware. I haven't seen
>> this working on newer graphics cards models with the opensource
>> drivers to the present day :(
> 
> I think that's one of the reasons of Greg's post.
> 
> (...)
>> if those companies can't use their own closed proprietary drivers
>> utilizing patented routines they are "forced" to use
> 
> You're wrong here. If they have patented routines, they don't need
> their drivers to be closed, since there routines are protected by
> patents. And even if they are not patented, not releasing the source
> will not prevent a competitor from disassembling the code anyway.
> So there's really no point in remaining closed. Some of them might
> have signed NDAs before using some technologies, but by this time,
> they should have sorted that our.

Willy, you make a bold assertion here. Your assertion would hold a
lot more weight if you defended it with some facts.

>> they might think over it and switch to another operating system ...
> 
> Do you know many products with closed Linux drivers which are not
> supported by at least one closed OS ? If they chose to support
> Linux, it's not for your pleasure, just because they know they will
> sell 5-10% more when a penguin is stuck on the box.

That is why there are the closed, and flakey, drivers for so many
products. Rather than make ideological assertions sit down and prove
your points. Address cases where there is an intellectual property
holder involved who has chosen Trade Secret rather than Patent as a
protection on their proprietary code. Show how they will stay in
business if they give away their code. Presume that their modules are
in clean enough shape that making money with a profitable service desk
is not going to fly.

> Willy

{^_^}   Jo
--
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/