> As longtime subscribers to acpi-devel know, this seems to come up every few
> months, but the criticisms mentioned in this week's lwn.net kernel
> development summary (http://lwn.net/2002/0124/kernel.php3) prompt me to
> respond, lest my silence be taken for capitulation. ;-)
I'm sorry if you, or the other Linux ACPI developers, felt attacked by what
was written - that certainly wasn't the intent. Everything that appeared
in LWN had to do with the ACPI specification, and not any particular
implementation. I don't doubt that I could have written it in a clearer,
more even-handed way.
It may well be that the concerns over ACPI are overblown. It is true,
however, that the concerns exist and are widely shared. It would be
worthwhile to have a discussion on why people shouldn't worry. What
controls are there on the things AML code can do? What reasons are there
to expect that ACPI code will be more reliable than any other sort of BIOS
code?
Increasingly, it seems that it will not be possible to use modern hardware
without ACPI. So, in a sense, the point will be moot. Certainly it is
only a good thing that Linux has a high-quality ACPI implementation in the
works, so that users will have the option to use it. I expect that most
will happily run it and look no further.
But that doesn't change the fact that a lot of people do not like the ACPI
standard. There is some selling yet to be done if that dislike is to be
overcome.
jon
Jonathan Corbet
Executive editor, LWN.net
corbet@lwn.net
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/