From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1764047AbYGBLtn (ORCPT ); Wed, 2 Jul 2008 07:49:43 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756459AbYGBLt1 (ORCPT ); Wed, 2 Jul 2008 07:49:27 -0400 Received: from [194.117.236.238] ([194.117.236.238]:37616 "EHLO heracles.linux360.ro" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1759066AbYGBLtZ (ORCPT ); Wed, 2 Jul 2008 07:49:25 -0400 Date: Wed, 2 Jul 2008 14:48:20 +0300 From: Eduard - Gabriel Munteanu To: Matthew Garrett Cc: Justin Mattock , "Rafael J. Wysocki" , Linux Kernel Mailing List , ACPI Devel Maling List Subject: Re: dsdt buggy acpi Message-ID: <20080702144820.29f7d43d@linux360.ro> In-Reply-To: <20080702100935.GA699@srcf.ucam.org> References: <200807011619.53339.rjw@sisk.pl> <20080702082555.0959ef2b@linux360.ro> <20080702100935.GA699@srcf.ucam.org> X-Mailer: Claws Mail 3.4.0 (GTK+ 2.12.1; x86_64-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 2 Jul 2008 11:09:35 +0100 Matthew Garrett wrote: > On Wed, Jul 02, 2008 at 08:25:55AM +0300, Eduard - Gabriel Munteanu > wrote: > > > Just one note here: DSDTs have nothing to do with the kernel. This > > is just broken firmware. The most one can do _in-kernel_ is > > blacklist some functionality or create a workaround, but this only > > happens for widely used stuff. Broken DSDTs aren't widely used > > stuff, they are written by the machine's vendor (the laptop's > > manufacturer for example, but this could be different for desktops) > > and differ a lot from one machine to another. > > 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. 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.