From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andi Kleen Subject: Re: RE: ACPI -- Workaround for broken DSDT Date: Thu, 5 Feb 2004 08:29:26 +0100 Sender: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Message-ID: <20040205082926.660974d2.ak@suse.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Errors-To: acpi-devel-admin-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , List-Archive: To: "Brown, Len" Cc: scott-j3vAvQ9dNB9ByuSxxbvQtw@public.gmane.org, acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: linux-acpi@vger.kernel.org On Thu, 5 Feb 2004 00:15:36 -0500 "Brown, Len" wrote: > > Re: what does windows do? > Windows doesn't have to do anything. By being first to ship ACPI, that > implementation provided the defacto ACPI compliance test to which all > BIOS' are tested -- even if that implementation is not ACPI spec I don't think that's completely true. A lot of the DSDTs I looked at had special cases for Win98,Win2000,WinXP. Undoubtedly the next windows versions will also require special cases in the AML. Longer term all we can hope for is that the next generation of BIOS will also have a case for Linux. > compliant. No, only under dire circumstances will we emulate Windows > bugs in Linux. A little bit more bug-to-bug compatibility surely couldn't hurt, even when Microsoft isn't even compatible to themsevles. Like we already have the RELAXED_AML mode and everybody enables it ... It just isn't often relaxed enough. -Andi ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn