From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Garrett Subject: Re: linux-next: Tree for June 13: IO APIC breakage on HP nx6325 Date: Sun, 29 Jun 2008 20:23:53 +0100 Message-ID: <20080629192353.GA9132@srcf.ucam.org> References: <20080613232214.394fd6fd.sfr@canb.auug.org.au> <200806262152.02099.rjw@sisk.pl> <200806291600.29059.rjw@sisk.pl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from cavan.codon.org.uk ([93.93.128.6]:57021 "EHLO vavatch.codon.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752752AbYF2TYP (ORCPT ); Sun, 29 Jun 2008 15:24:15 -0400 Content-Disposition: inline In-Reply-To: Sender: linux-next-owner@vger.kernel.org List-ID: To: "Maciej W. Rozycki" Cc: "Rafael J. Wysocki" , Ingo Molnar , Stephen Rothwell , linux-next@vger.kernel.org, LKML , Thomas Gleixner , ACPI Devel Maling List , Len Brown 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. -- Matthew Garrett | mjg59@srcf.ucam.org