From: Matthew Garrett <mjg59@srcf.ucam.org>
To: Henrique de Moraes Holschuh <hmh@hmh.eng.br>
Cc: Len Brown <lenb@kernel.org>, Thomas Renninger <trenn@suse.de>,
Arjan van de Ven <arjan@linux.intel.com>,
linux-acpi <linux-acpi@vger.kernel.org>,
"Moore, Robert" <robert.moore@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andi Kleen <ak@linux.intel.com>,
Christian Kornacker <ckornacker@suse.de>
Subject: Re: ACPI OSI disaster on latest HP laptops - critical temperature shutdown
Date: Sat, 2 Aug 2008 16:41:14 +0100 [thread overview]
Message-ID: <20080802154114.GA28879@srcf.ucam.org> (raw)
In-Reply-To: <20080802143833.GC14069@khazad-dum.debian.net>
On Sat, Aug 02, 2008 at 11:38:33AM -0300, Henrique de Moraes Holschuh wrote:
> Yes. IBM ThinkPads store the result of each version test separately, and I
> recall I saw at least one DSDT code path that didn't test all of them in
> order to select a branch of code to run.
As an example, here's a section from the T61:
If (\_OSI ("Windows 2001"))
{
Store (0x01, \WNTF)
Store (0x01, \WXPF)
Store (0x00, \WSPV)
}
If (\_OSI ("Windows 2001 SP1"))
{
Store (0x01, \WSPV)
}
If (\_OSI ("Windows 2001 SP2"))
{
Store (0x02, \WSPV)
}
And then later:
If (LAnd (\WXPF, LGreaterEqual (\WSPV, 0x01)))
{
PPMS (0x02)
}
The only way WXPF can be non-zero and WSPV can be greater or equal to
one is if more than one of those tests succeeded.
> > Not all BIOSes would support this, so we'd need to support the Windows
> > workarounds anyway. At that point, there's no real benefit in having
> > multiple codepaths.
>
> Sorry, but I will disagree.
>
> Anything that can help in the future with the vendors that are better at
> Linux support is a good thing. You are right that we will still have to
> deal with the others, but there are such things as vendor-specific windows
> workarounds (they didn't want to change their firmware, or they couldn't, or
> the others didn't care to add the workaround, etc). If that vendor uses the
> "NotWindows" OSI correctly, we would not need to take any special action.
Allowing vendors to special-case Linux means that we have to have a
special-case path for the minority of vendors who ask for this. It's
added complexity and we don't actually gain anything from it.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2008-08-02 15:41 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-24 15:27 ACPI OSI disaster on latest HP laptops - critical temperature shutdowns Thomas Renninger
2008-07-24 15:42 ` Arjan van de Ven
2008-07-25 0:04 ` ACPI OSI disaster on latest HP laptops - critical temperature shutdown Len Brown
2008-07-25 10:44 ` Andi Kleen
2008-07-25 11:19 ` Thomas Renninger
2008-07-25 15:26 ` Rafael J. Wysocki
2008-07-26 12:42 ` Andi Kleen
[not found] ` <alpine.LFD.1.10.0807261406230.2958@localhost.localdomain>
2008-08-01 21:08 ` Len Brown
2008-08-03 17:23 ` Thomas Renninger
[not found] ` <alpine.LFD.1.10.0807250948320.3884@localhost.localdomain>
2008-08-01 21:07 ` Len Brown
2008-08-01 22:36 ` Henrique de Moraes Holschuh
2008-08-02 5:42 ` Matthew Garrett
2008-08-02 14:38 ` Henrique de Moraes Holschuh
2008-08-02 14:44 ` Norbert Preining
2008-08-02 14:51 ` Henrique de Moraes Holschuh
2008-08-04 21:33 ` Norbert Preining
2008-08-02 15:41 ` Matthew Garrett [this message]
2008-08-02 17:49 ` Henrique de Moraes Holschuh
2008-08-02 19:49 ` Matthew Garrett
[not found] ` <alpine.LFD.1.10.0807261409290.2958@localhost.localdomain>
2008-08-01 21:08 ` Len Brown
2008-07-25 22:10 ` Eric Piel
2008-07-25 22:19 ` Moore, Robert
[not found] ` <alpine.LFD.1.10.0807261311420.2958@localhost.localdomain>
2008-08-01 21:07 ` Len Brown
[not found] ` <alpine.LFD.1.10.0807261434380.2958@localhost.localdomain>
2008-08-01 21:02 ` ACPI OSI disaster on latest HP laptops - critical temperature shutdowns Len Brown
2008-08-13 19:22 ` Pavel Machek
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=20080802154114.GA28879@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=ak@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=ckornacker@suse.de \
--cc=hmh@hmh.eng.br \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.moore@intel.com \
--cc=trenn@suse.de \
/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