[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20080629192353.GA9132@srcf.ucam.org>
Date: Sun, 29 Jun 2008 20:23:53 +0100
From: Matthew Garrett <mjg59@...f.ucam.org>
To: "Maciej W. Rozycki" <macro@...ux-mips.org>
Cc: "Rafael J. Wysocki" <rjw@...k.pl>, Ingo Molnar <mingo@...e.hu>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
Thomas Gleixner <tglx@...utronix.de>,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Len Brown <lenb@...nel.org>
Subject: Re: linux-next: Tree for June 13: IO APIC breakage on HP nx6325
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@...f.ucam.org
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists