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: <3d57814d0612310503r282404afgd9b06ca57f44ab3c@mail.gmail.com>
Date:	Sun, 31 Dec 2006 23:03:27 +1000
From:	"Trent Waddington" <trent.waddington@...il.com>
To:	"Bernd Petrovitsch" <bernd@...mix.at>
Cc:	"Erik Mouw" <erik@...ddisk-recovery.com>, Valdis.Kletnieks@...edu,
	"Giuseppe Bilotta" <bilotta78@...pop.com>,
	linux-kernel@...r.kernel.org
Subject: Re: Open letter to Linux kernel developers (was Re: Binary Drivers)

> > On Thu, Dec 21, 2006 at 01:16:15PM -0500, Valdis.Kletnieks@...edu wrote:
> > > At least nVidia *does* actually Get It, they just don't have a choice in
> > > implementing it, because all their current hardware includes patents that
> > > they licensed from other companies

What makes you think they "get it"?

In a recent interview
(http://bsdtalk.blogspot.com/2006/07/bsdtalk054-interview-with-andy-ritger.html)
the nvidia developer had this to say:

"Quite honestly we have a lot of ip sorrounding both our hardware and
our software. And so the driver we provide is binary only, ya know, to
protect that intellectual property. You know, I guess, on a software
side, so much of what we do, err, of the code that comprises that
drivers is common and leveraged across all the operating systems and I
think that is a big benefit. You know we are able to accomplish a lot
with a fairly small, err, unix specific engineering team because we're
able to leverage so much common code. Ya know, that really is a big
win for us and our users, and so, ya know, we provide a binary only
driver to protect that ip. Umm, that said, we do try to, ya know,
provide source for, err, ya know, for things when it makes sense and
its possible to do so. I guess for our various unix graphics drivers,
the interface between *cough* excuse me, the core of the binary, err
the core of the kernel module is operating system neutral .. is
shipped binary only but anything that, ya know, interacts directly
with, with unix kernel, be it linux or freebsd or whatever, we provide
the source code to that interface layer. Similarly, err, I guess, up
in user space, umm, you know, we were talking either about, umm, the
nvida X extension and our control panel nvidia-settings. The source
code for that is provided as GPL. We provide a command line tool
nvidia-xconfig for manipulating your xconfiguration files. We provide
that as GPL. So we do try to provide source code to those sorts of
utilities and things like that when it makes sense. Umm, but the core
of our driver, we only provide as binary."

Yeah, really sounds like he "gets it".

Why don't you release source?  To protect the intellectual property.
Well, duh!  That's why everyone holds back source.  So allow me to
translate..

Why don't you release source?  Because we don't believe in freedom, we
don't "get it" and we don't want you to have it.

That wasn't some marketting stooge they were interviewing either, it
was two of the guys who work on the unix porting team for the nvidia
drivers.

They don't get it.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ