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]
Date:	Tue, 30 Jan 2007 15:29:02 -0800
From:	Roland Dreier <rdreier@...co.com>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Greg KH <greg@...ah.com>, linux-kernel@...r.kernel.org
Subject: Re: Free Linux Driver Development!

 > You were complaining about drivers that work on only one
 > platform. Thus, I asked for list of said drivers, drivers that break
 > Greg's pledge.

When did I ever say "one platform"?  If I did, it was an error -- I've
tried to consistently talk about not every platform.

 > I'm betting they are uniformly ancient ISA or m68k or whatnot drivers.

So what?  Greg didn't restrict his offer to "mainstream" devices.  And
Greg said "[the driver] will be automatically kept up to date and
working through all Linux kernel API changes."  Not "we'll maintain
the driver until we lose interest."  And anyway, if I dig for a few
minutes I find modern mainstream stuff like ipw2200 that is seemingly
x86-only.  (Although of course ipw2200 is straight from Intel)

 > And hooray for shifting arguments.  If this is your summary of the
 > thread, do you now concede that Greg was not being disingenuous?  Open
 > specs was not the sum toto of Greg's piece.

Perhaps "disingenous" was the wrong choice of word, though, since you
and Greg seem to sincerely believe that a spec dump is all that a
vendor needs to do.  I'll concede that maybe I should have used the
word "naive" instead.  But I absolutely feel that Greg should not be
making promises on behalf of "the Linux kernel community."

Go back and reread Greg's original email.  He said:

 > All that is needed is some kind of specification that describes how
 > your device works, or the email address of an engineer that is willing
 > to answer questions every once in a while. A few sample devices might
 > be good to have so that debugging doesn't have to be done by email,
 > but if necessary, that can be done.

Let me repeat Greg's words one more time: "All that is needed is some
kind of specification."  So I honestly don't know what you mean by
"open specs was not the sum toto of Greg's piece."

Here is what he promised once that spec is released:

 > In return, you will receive a complete and working Linux driver that
 > is added to the main Linux kernel source tree.

...

 > This driver will then be automatically included in all Linux
 > distributions, including the "enterprise" ones. It will be
 > automatically kept up to date and working through all Linux kernel
 > API changes. This driver will work with all of the different CPU
 > types supported by Linux, the largest number of CPU types supported
 > by any operating system ever before in the history of computing.

...

 > As for support, the driver will be supported through email by the
 > original developers, when they can help out, and by the
 > "enterprise" Linux distributors as part of their service agreements
 > with their customers.

...

 > This offer is in effect for all different types of devices, from USB
 > toys to PCI video devices to high-speed networking cards. If you
 > manufacture it, we can get Linux drivers working for it.

To me, it's clear that historically the community hasn't delivered on
this.  So I don't like promising something that we haven't been able
to follow through on in the past.  If a vendor takes Greg's offer, and
then the community, for whatever reason, fails to deliver on
everything, then that makes us all (including me!) look bad just
because of Greg's hyperbolic promises.

 - R.
-
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