From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760649AbYHAVIs (ORCPT ); Fri, 1 Aug 2008 17:08:48 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760576AbYHAVIU (ORCPT ); Fri, 1 Aug 2008 17:08:20 -0400 Received: from vms173001pub.verizon.net ([206.46.173.1]:60848 "EHLO vms173001pub.verizon.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1760283AbYHAVIR (ORCPT ); Fri, 1 Aug 2008 17:08:17 -0400 Date: Fri, 01 Aug 2008 17:08:08 -0400 (EDT) From: Len Brown Subject: Re: ACPI OSI disaster on latest HP laptops - critical temperature shutdown In-reply-to: X-X-Sender: lenb@localhost.localdomain To: "Rafael J. Wysocki" Cc: Thomas Renninger , Arjan van de Ven , linux-acpi , "Moore, Robert" , Linux Kernel Mailing List , Andi Kleen , Christian Kornacker Message-id: MIME-version: 1.0 Content-type: TEXT/PLAIN; charset=US-ASCII References: <200807241727.41715.trenn@suse.de> <200807251319.12786.trenn@suse.de> <200807251726.14366.rjw@sisk.pl> User-Agent: Alpine 1.10 (LFD 962 2008-03-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org [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 > >