From: Disconnect <lkml@sigkill.net>
To: lkml <linux-kernel@vger.kernel.org>
Subject: Re: ACPI broken... again!
Date: 17 Jun 2003 11:12:08 -0400 [thread overview]
Message-ID: <1055862728.15330.16.camel@slappy> (raw)
In-Reply-To: <20030617144443.GA27558@codeblau.de>
On Tue, 2003-06-17 at 10:44, Felix von Leitner wrote:
> Linux 2.5.70 and above have broken ACPI. Again. This is my fifth
> machine on which I try ACPI, two notebooks and three desktops, chipsets
> from Intel, VIA and SiS, no matter, ACPI still breaks 'em all.
> Why oh why is ACPI so horrendously broken?
Because its a moderately bad spec that your vendor implemented to deal
with a horrid redmond interpreter. (And, to make things worse, the
linux-acpi team specifically insists on implementing the spec, not the
reality. "We refuse to be bug-for-bug compatible with the other major
implementation." So linux-acpi is "right" but redmond-acpi is tested
and actually works.)
> And more to the point: if it _is_ this broken, why ship it at all? I
> don't recall a single moment where ACPI did anything good for me, only
I'm kinda fond of battery status. And pci interrupt routing (convenient,
that..) and the half-dozen or so important other functions that even a
half-broken ACPI provides on my main machine (laptop, no APM support at
all.) And as a side note, especially on laptops, the DSDT (bios "talk
to acpi-managed hardware like this" bytecode) tends to be dramatically
broken. acpi.sf.net has info on patching it, some pre-patched tables,
etc.
Hate it? Well... that'd be why its a configure option.
--
Disconnect <lkml@sigkill.net>
next prev parent reply other threads:[~2003-06-17 14:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-17 14:44 ACPI broken... again! Felix von Leitner
2003-06-17 15:12 ` Disconnect [this message]
2003-06-17 16:03 ` Ducrot Bruno
-- strict thread matches above, loose matches on Subject: below --
2003-06-17 17:10 Grover, Andrew
2003-06-17 18:02 ` Yaroslav Rastrigin
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=1055862728.15330.16.camel@slappy \
--to=lkml@sigkill.net \
--cc=linux-kernel@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.