Re: [2.6 patch] let broken drivers depend on BROKEN{,ON_SMP}

[Rob Landley]

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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/