From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Rafael J. Wysocki" Subject: Re: linux-next: Tree for June 13: IO APIC breakage on HP nx6325 Date: Sun, 29 Jun 2008 21:31:02 +0200 Message-ID: <200806292131.03859.rjw@sisk.pl> References: <20080613232214.394fd6fd.sfr@canb.auug.org.au> <20080629192353.GA9132@srcf.ucam.org> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Return-path: Received: from ogre.sisk.pl ([217.79.144.158]:45639 "EHLO ogre.sisk.pl" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752716AbYF2T3w (ORCPT ); Sun, 29 Jun 2008 15:29:52 -0400 In-Reply-To: <20080629192353.GA9132@srcf.ucam.org> Content-Disposition: inline Sender: linux-next-owner@vger.kernel.org List-ID: To: Matthew Garrett Cc: "Maciej W. Rozycki" , Ingo Molnar , Stephen Rothwell , linux-next@vger.kernel.org, LKML , Thomas Gleixner , ACPI Devel Maling List , Len Brown On Sunday, 29 of June 2008, Matthew Garrett wrote: > On Sun, Jun 29, 2008 at 08:05:42PM +0100, Maciej W. Rozycki wrote: > > > It is the reverse -- checking the DSDT ID is coarser, matching all the > > systems that use the broken firmware. With DMI we may face both false > > positives and false negatives which imply further maintenance actions. > > Please note as proved over the years understanding of these issues seems > > to be problematic for people, so the result may be another round of > > discussions reinventing the wheel in a couple of years' time or so. > > The DSDT can't be updated without the BIOS being updated, and the DMI > information gives us a BIOS version string that can be matched against > if a fixed version is ever released. I'd be in favour of doing it with > DMI on the grounds that it's how we already handle machine-specific > quirks rather than adding new code to do it. I violently agree. Thanks, Rafael