From: Rob Landley <rob@landley.net>
To: Bill Davidsen <davidsen@tmr.com>
Cc: Linux-Kernel@vger.kernel.org
Subject: Re: [2.6 patch] let broken drivers depend on BROKEN{,ON_SMP}
Date: Sun, 17 Aug 2003 05:39:44 -0400 [thread overview]
Message-ID: <200308170539.45145.rob@landley.net> (raw)
In-Reply-To: <Pine.LNX.3.96.1030813165635.12417K-100000@gatekeeper.tmr.com>
On Wednesday 13 August 2003 17:06, Bill Davidsen wrote:
> 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.
You are aware that this would probably take more effort to keep up to date
than the code itself, right? And that one spreadsheet couldn't
simultaneously be accurate for 2.4, 2.6, -ac, -mm, -redhat, -suse...
And how would you keep track of weird "there's a good driver for that, but you
have to apply this patch" cases? (Isn't this sort of thing what the various
bug database efforts are for?)
Will you be tracking cases that only show up on big-endian 64 bit platforms
that have more than one PCI bus? How about situations where the driver works
fine except when you use it in a system with a certain type of USB controller
and do not have a PS/2 mouse plugged into the system. (Yes, really.) How
about if it works but doesn't come back after an APM suspend? Do you tag it
as broken if it works on 95% of the systems out there, but not all of them,
based on stuff the Bios did before the Linux kernel even got loaded?
I'm currently trying to figure out why APM doesn't work on my new thinkpad.
Is APM broken? It freezes my thinkpad solid. The exact same Red Hat 9
kernel worked fine on the toshiba that got rained on...
I'm now playing with software suspend in 2.6-test. You not only have to
enable software suspend in the power management menu, and you have to go into
ACPI and enable ACPI support, but you also have to enable ACPI sleep state
support. Right. Documentation/swsusp.txt didn't mention that, and there's a
kconfig dependency missing here somewhere. I'm much more interested in
getting it to work than marking it broken for posterity...
Rob
next prev parent reply other threads:[~2003-08-17 20:15 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
2003-08-17 9:39 ` Rob Landley [this message]
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=200308170539.45145.rob@landley.net \
--to=rob@landley.net \
--cc=Linux-Kernel@vger.kernel.org \
--cc=davidsen@tmr.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