linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bill Davidsen <davidsen@tmr.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Tomas Szepe <szepe@pinerecords.com>, Adrian Bunk <bunk@fs.tum.de>,
	John Bradford <john@grabjohn.com>,
	Riley@Williams.Name, Linux-Kernel@vger.kernel.org
Subject: Re: [2.6 patch] let broken drivers depend on BROKEN{,ON_SMP}
Date: Wed, 13 Aug 2003 17:06:06 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.3.96.1030813165635.12417K-100000@gatekeeper.tmr.com> (raw)
In-Reply-To: <20030813153144.GA10579@gtf.org>

On Wed, 13 Aug 2003, Jeff Garzik wrote:

> On Wed, Aug 13, 2003 at 10:50:12AM -0400, Bill Davidsen wrote:

> > If you get a bunch of compiler errors without a clear indication that the
> > driver is known to have problems, it is more likely to produce a "Linux is
> > crap" reaction. With the problems Windows is showing this week, I'd like
> > to show Linux as the reliable alternative, not whatever MS is saying about
> > hacker code this week.
> 
> The people who want Linux to be reliable won't be compiling their own
> kernels, typically.  Because, the people that _do_ compile their own
> kernels have sense enough to disable broken drivers :)  That's what Red
> Hat, SuSE, and others do today.

Disabling broken drivers is fine, identifying them is nice, too. When I
was deciding which gigE cards to use, I found that all drivers in the 2.4
kernel were not equal. Some didn't compile with my config, some compiled
but had runtime problems, etc.

It would be nice if there were some neat 3-D shreadsheet type thing
listing all drivers, all architectures, UP vs. SMP, and a status such as
WORKS, DOESN'T COMPILE, REPORTED PROBLEMS (SLOW|ERRORS|PANICS) and the
like. I don't even know where to find a good open source 3-D spreadsheet,
and the data certainly is scattered enough to be a project in itself,
chasing a moving target.

A BROKEN config isn't a perfect solution (fixing the drivers is), but it
would help in some cases, and I don't see that it would hurt, and more
information is usually better.

Not my original idea, my ego won't be hurt if it doesn't happen.

-- 
bill davidsen <davidsen@tmr.com>
  CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.


  parent reply	other threads:[~2003-08-13 21:28 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-30  9:11 [2.6 patch] let broken drivers depend on BROKEN{,ON_SMP} John Bradford
2003-07-30 10:44 ` Adrian Bunk
2003-07-30 16:04   ` Tomas Szepe
2003-07-30 16:18     ` Adrian Bunk
2003-07-31  9:15       ` Tomas Szepe
2003-08-02 19:47         ` Adrian Bunk
2003-08-13 14:50         ` Bill Davidsen
2003-08-13 15:31           ` Jeff Garzik
2003-08-13 19:17             ` Adrian Bunk
2003-08-13 21:06             ` Bill Davidsen [this message]
2003-08-17  9:39               ` Rob Landley
2003-08-18 23:03                 ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2003-08-17 21:27 John Bradford
2003-08-14  5:28 John Bradford
2003-08-13 20:40 John Bradford
2003-08-13 21:03 ` Adrian Bunk
2003-07-31  9:41 John Bradford
2003-08-02 19:48 ` Adrian Bunk
2003-07-30 11:29 John Bradford
2003-07-30 11:37 ` Adrian Bunk
2003-07-30 11:53   ` Jan Evert van Grootheest
2003-07-29 19:59 Adrian Bunk
2003-07-30  7:44 ` Riley Williams

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.3.96.1030813165635.12417K-100000@gatekeeper.tmr.com \
    --to=davidsen@tmr.com \
    --cc=Linux-Kernel@vger.kernel.org \
    --cc=Riley@Williams.Name \
    --cc=bunk@fs.tum.de \
    --cc=jgarzik@pobox.com \
    --cc=john@grabjohn.com \
    --cc=szepe@pinerecords.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).