[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.55.0806292115200.22548@cliff.in.clinika.pl>
Date: Sun, 29 Jun 2008 21:16:38 +0100 (BST)
From: "Maciej W. Rozycki" <macro@...ux-mips.org>
To: Matthew Garrett <mjg59@...f.ucam.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, 29 Jun 2008, Matthew Garrett wrote:
> > Is the DMI ID *guaranteed* to be changed with an update to the DSDT?
>
> The BIOS version is, yes.
Good to know, thanks.
> > Anyway, you cannot imply from a given DMI ID a broken DSDT is present, so
> > you will have to repeat the experience of adding another DMI ID whenever a
> > user hits this broken DSDT with another piece of hardware. As long as you
> > are able to pull this piece of information from that user, that is...
>
> These are the only two pieces of hardware ever reported to have this
> problem. Nobody appears to have demonstrated it on any other HP systems,
> and any non-HP systems would have a different identifier string. With
> the SB400 being superceded, I don't expect us to see any more machines
> with the same ID.
Fair enough. As I wrote, I'll send an update shortly.
Maciej
--
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