mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
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>,
	Andi Kleen <ak@linux.intel.com>,
	Christian Kornacker <ckornacker@suse.de>
Subject: Re: ACPI OSI disaster on latest HP laptops - critical temperature shutdown
Date: Fri, 01 Aug 2008 17:08:08 -0400 (EDT)	[thread overview]
Message-ID: <alpine.LFD.1.10.0808011708010.3011@localhost.localdomain> (raw)
In-Reply-To: <alpine.LFD.1.10.0807261406230.2958@localhost.localdomain>

[yet another resend]

On Sat, 26 Jul 2008, Len Brown wrote:

> 
> 
> On Fri, 25 Jul 2008, Rafael J. Wysocki wrote:
> 
> > On Friday, 25 of July 2008, Thomas Renninger wrote:
> > > On Friday 25 July 2008 02:04:32 Len Brown wrote:
> > [--snip--]
> > > 
> > > Len, this is not about the thermal zone, it is just
> > > a real-world example of something I told you will happen
> > > if Linux stays _OSI transparent with Windows.
> > > 
> > > This is about that they have to provide a BIOS hot-fix for
> > > VISTA or VISTA SP and thus breaking Linux because there
> > > is no way to distinguish anymore.
> > > Windows 2007 likely will have that fixed and they provide
> > > a sane _CRT trip point again.
> > > This is an example of Windows versions workarounds that could
> > > get much more complex, like initializing HW differently or
> > > whatever.
> > > _OSI is used by vendors as a convenient possibility to
> > > adjust/workaround Windows bugs in their BIOSes, without
> > > the need to pay Millions to Microsoft to fix their things.
> > 
> > This is a valid point, IMO.
> > 
> > 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.
> 
> I belive that the AML Thomas shared does not
> illustrate a Vista bug workaround in a BIOS.
> Rather it is simply a BIOS bug that Vista doesn't catch.
> 
> -Len
> 
> 

  parent reply	other threads:[~2008-08-01 21:08 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 [this message]
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=alpine.LFD.1.10.0808011708010.3011@localhost.localdomain \
    --to=lenb@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=arjan@linux.intel.com \
    --cc=ckornacker@suse.de \
    --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

Powered by JetHome