| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Sun, 29 Jun 2008 21:03:29 +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: > 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. Is the DMI ID *guaranteed* to be changed with an update to the DSDT? 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... 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