From: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
To: "Justin Mattock" <justinmattock@gmail.com>
Cc: "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 08:25:55 +0300 [thread overview]
Message-ID: <20080702082555.0959ef2b@linux360.ro> (raw)
In-Reply-To: <dd18b0c30807010918p48cfbe2bnb7e4a2bf00a01638@mail.gmail.com>
On Tue, 1 Jul 2008 16:18:45 +0000
"Justin Mattock" <justinmattock@gmail.com> wrote:
> Cool; thanks.
> I'll check that out and see where and how I can locate the dsdt
> manufacture number, then see if I can fix the broken dsdt error and
> apply this to the kernel and see what happens.
> regards;
Just one note here: DSDTs have nothing to do with the kernel. This is
just broken firmware. The most one can do _in-kernel_ is blacklist some
functionality or create a workaround, but this only happens for widely
used stuff. Broken DSDTs aren't widely used stuff, they are written by
the machine's vendor (the laptop's manufacturer for example, but this
could be different for desktops) and differ a lot from one machine to
another.
Eduard
next prev parent reply other threads:[~2008-07-02 5:26 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 [this message]
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
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=20080702082555.0959ef2b@linux360.ro \
--to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox