From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
Cc: Justin Mattock <justinmattock@gmail.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: dsdt buggy acpi
Date: Wed, 2 Jul 2008 12:55:27 +0100 [thread overview]
Message-ID: <20080702115527.GA3396@srcf.ucam.org> (raw)
In-Reply-To: <20080702144820.29f7d43d@linux360.ro>
On Wed, Jul 02, 2008 at 02:48:20PM +0300, Eduard - Gabriel Munteanu wrote:
> On Wed, 2 Jul 2008 11:09:35 +0100
> Matthew Garrett <mjg59@srcf.ucam.org> wrote:
> > We've made a huge number of workarounds for buggy DSDT
> > implementations.
>
> Of course, I myself used a custom DSDT for my laptop. But I was saying
> that these workarounds generally do not belong to the kernel realm.
Of course they do. Nothing else is going to fix them up.
> This isn't the regular "Pentium F00F bug" stuff; instead bugs in DSDTs
> consist of compiling issues, non-standard compliant, plainly bad
> code, Windows-only stuff, which can all be unique for every model of a
> laptop for example. While the kernel may be able to get around some of
> that stuff, the kernel won't have any Asus, Acer etc. specific
> workarounds.
Windows doesn't have any Asus/Acer/whatever workarounds either. We just
need to be compatible with the Windows implementation. There's a
minority of cases where that isn't good enough, but almost every DSDT
issue can (and should) be handled by Linux if the machine works under
Windows.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-07-02 11:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 6:39 dsdt buggy acpi Justin Mattock
2008-07-01 14:19 ` Rafael J. Wysocki
2008-07-01 16:18 ` Justin Mattock
2008-07-02 5:25 ` Eduard - Gabriel Munteanu
2008-07-02 6:16 ` Justin Mattock
2008-07-02 10:09 ` Matthew Garrett
2008-07-02 11:48 ` Eduard - Gabriel Munteanu
2008-07-02 11:55 ` Matthew Garrett [this message]
2008-07-02 16:30 ` Justin Mattock
2008-07-02 16:35 ` Matthew Garrett
2008-07-02 17:37 ` Justin Mattock
2008-07-04 11:32 ` Alexey Starikovskiy
2008-07-04 16:23 ` Justin Mattock
2008-07-04 21:45 ` Justin Mattock
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=20080702115527.GA3396@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=eduard.munteanu@linux360.ro \
--cc=justinmattock@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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.