From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: dsdt buggy acpi Date: Wed, 2 Jul 2008 12:55:27 +0100 Message-ID: <20080702115527.GA3396@srcf.ucam.org> References: <200807011619.53339.rjw@sisk.pl> <20080702082555.0959ef2b@linux360.ro> <20080702100935.GA699@srcf.ucam.org> <20080702144820.29f7d43d@linux360.ro> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from cavan.codon.org.uk ([93.93.128.6]:59621 "EHLO vavatch.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754165AbYGBLzb (ORCPT ); Wed, 2 Jul 2008 07:55:31 -0400 Content-Disposition: inline In-Reply-To: <20080702144820.29f7d43d@linux360.ro> Sender: linux-acpi-owner@vger.kernel.org List-Id: linux-acpi@vger.kernel.org To: Eduard - Gabriel Munteanu Cc: Justin Mattock , "Rafael J. Wysocki" , Linux Kernel Mailing List , ACPI Devel Maling List On Wed, Jul 02, 2008 at 02:48:20PM +0300, Eduard - Gabriel Munteanu wrote: > On Wed, 2 Jul 2008 11:09:35 +0100 > Matthew Garrett wrote: > > We've made a huge number of workarounds for buggy DSDT > > implementations. > > Of course, I myself used a custom DSDT for my laptop. But I was saying > that these workarounds generally do not belong to the kernel realm. Of course they do. Nothing else is going to fix them up. > This isn't the regular "Pentium F00F bug" stuff; instead bugs in DSDTs > consist of compiling issues, non-standard compliant, plainly bad > code, Windows-only stuff, which can all be unique for every model of a > laptop for example. While the kernel may be able to get around some of > that stuff, the kernel won't have any Asus, Acer etc. specific > workarounds. Windows doesn't have any Asus/Acer/whatever workarounds either. We just need to be compatible with the Windows implementation. There's a minority of cases where that isn't good enough, but almost every DSDT issue can (and should) be handled by Linux if the machine works under Windows. -- Matthew Garrett | mjg59@srcf.ucam.org