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 14:50:49 -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!

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

Anyway, grepping for stuff like BROKEN or !64BIT or X86 in the Kconfig
dependencies under drivers/ finds tons of hits.  I don't have time to
scan through and figure out which meet your criteria, and I honestly
don't know how enterprise distros decide what to support.  For example
RHEL4 seems to ship aha152x (which depends on ISA && SCSI && !64BIT),
but what will RH do if someone actually wants support for it?

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.

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