public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Thomas Renninger <trenn@suse.de>, Len Brown <lenb@kernel.org>,
	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>,
	Christian Kornacker <ckornacker@suse.de>
Subject: Re: ACPI OSI disaster on latest HP laptops - critical temperature shutdown
Date: Sat, 26 Jul 2008 05:42:27 -0700	[thread overview]
Message-ID: <488B1BB3.7010602@linux.intel.com> (raw)
In-Reply-To: <200807251726.14366.rjw@sisk.pl>


> If vendors use _OSI(Windows) to work around Windows bugs, we get broken
> automatically on those systems unless we put in some DMI-based hacks.

The general goal of ACPICA is to be bug-to-bug compatible with Windows.
So it might be needed for ACPICA to just emulate the respective bugs.

That said for this case I don't think that's needed, Linux just has to
detect the workarounds (which it already does I think)

-Andi


  reply	other threads:[~2008-07-26 12:42 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 [this message]
     [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
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=488B1BB3.7010602@linux.intel.com \
    --to=ak@linux.intel.com \
    --cc=arjan@linux.intel.com \
    --cc=ckornacker@suse.de \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rjw@sisk.pl \
    --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