[lkml]   [2004]   [Nov]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: 2.6.10-rc2 doesn't boot (if no floppy device)

On Mon, 22 Nov 2004, Len Brown wrote:
> I agree that the system should work properly even if the legacy device
> drivers are broken. Please understand, however, that the legacy device
> drivers _are_ broken. The BIOS via ACPI clearly tells them if the
> devices are present or not, and Linux isn't yet listening.

I really disagree.

I realize that you like ACPI, or you would have shot yourself long long

But I have a totally different view on things. To me, firmware is not
something cool to be used. It's a necessary evil, and it should be avoided
and mistrusted as far as humanly possible, because it is always buggy, and
we can't fix the bugs in it.

Yes, the current ACPI layer in the kernel is a lot better at working
around the bugs, and it's getting to the point where I suspect Linux
vendors actually decide that enabing ACPI by default causes fewer problems
than it solves. That clearly didn't use to be true.

> ACPI-compliant systems have three types of interrupts:

Stop right there.

"ACPI-compliant systems". The fact is, there is no such thing. There are
systems that users buy, and they are not "ACPI compliant", they are "one
implementation of ACPI that was tested with a single vendor usage test".

Call me cynical, but I believe in standards papers just about as much as I
believe in the voices in my attic that tell me to kill the Queen of

Papers is so much dead trees. The only thing that matters is real life.
And like it or not, real life does NOT implement standards properly, even
if the standards are well written and unambiguous (which also doesn't
actually happen in real life).

> If somebody bolts motherboard hardware on and doesn't tell ACPI about
> it, then they need to disable ACPI, which _owns_ configuration of
> motherboard devices when it is enabled.

No. The only thing that owns the motherboard is the user. ACPI shouldn't
get uppity.

> The damn good reason is that doing otherwise breaks systems.

And not doing it breaks systems.

See a pattern?

This is why I don't trust firmware. It's always buggy.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2009-11-18 23:46    [from the cache]
©2003-2011 Jasper Spaans