linux-kernel - Re: Free Linux Driver Development!

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:05:10 -0800
From:	Greg KH <greg@...ah.com>
To:	Roland Dreier <rdreier@...co.com>
Cc:	Jeff Garzik <jeff@...zik.org>, linux-kernel@...r.kernel.org
Subject: Re: Free Linux Driver Development!

On Tue, Jan 30, 2007 at 02:50:49PM -0800, Roland Dreier wrote:
>  > Which of these actively maintained and supported drivers work on only
>  > one platform[1], and are excluded from enterprise distros?  Can we
>  > truly count them as "many", as you repeatedly claim?
> 
> Why do we restrict this to actively maintained and supported drivers
> (I think abandonware drivers are highly relevant here...)?  And why
> are you asking about drivers that work on only one platform?  Greg
> promised support for every platform that has the right bus to plug a
> device into.  So things like drivers that don't work on SMP or 64-bit
> or big-endian platforms also violate that pledge, even if there's more
> than one 32-bit little-endian uniprocessor platform where the driver
> does work.

For almost all _new_ drivers, this is the case.  They are well supported
and build on all platforms.

Yes, there are plenty of old drivers that are marked BROKEN (look at the
scsi tree for some examples there), and some that still use cli (which
the kernel janitors keep trying to fix up but the very fact that no one
has the hardware to test their changes keeps that effort from going
anywhere.)  But that is not the case for new stuff, nor is it the case
for things I am offing here.

> I don't really understand why it's so hard to accept that sometimes
> even open specs aren't enough to get great Linux support.

Yeah, sometimes you really need someone who has the device in a machine
that still boots :)

thanks,

greg k-h
-
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/