public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: Len Brown <lenb@kernel.org>
Cc: 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>,
	Christian Kornacker <ckornacker@suse.de>
Subject: Re: ACPI OSI disaster on latest HP laptops - critical temperature shutdown
Date: Fri, 25 Jul 2008 03:44:35 -0700	[thread overview]
Message-ID: <4889AE93.4090601@linux.intel.com> (raw)
In-Reply-To: <alpine.LFD.1.10.0807241952270.6098@localhost.localdomain>

Len Brown wrote:
> Thomas,
> 
> re: OSI(Windows...)

Thomas,

I discussed this with Len here in Ottawa. First I fully agree with his 
reasoning for the current behaviour.

The main problem with OSI(Linux) is that it would be a quickly moving 
target so checking for it wouldn't really help the BIOSes.

Still there might be special cases where BIOSes will still check (e.g.
if they intend to work with specific distribution releases which might 
have specific bugs). Or to check for specific Linux features.

One way to do the later would be to define new OSI flags for specific
features. Haven't got a good proposal for that currently, but it's a 
possibility.

The other thing that could be done is to define OSI flags specific for
special distribution releases so BIOSes could potentially check for bugs
in SLED10 or RHWS5 or something like this, which are hopefully stable
in that behaviour doesn't move as quickly. The way to do that wouldn't
be to change the kernel though, but just specify them on the command 
line using acpi_osi=...

-Andi


  reply	other threads:[~2008-07-25 10:44 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 [this message]
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
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=4889AE93.4090601@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=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