Add DMI quirk for Intel DP55KG mainboard
in [Kernel]
|
Prev: Linux* is not supported on the Intel(R) Desktop Board DP55KG - Kernel still hangs upon reboot.
Next: drm: add KGDB/KDB support Add support for KDB entry/exit.
From: H. Peter Anvin on 4 Jan 2010 22:50 On 01/04/2010 06:15 PM, Robert Hancock wrote: > > Think you mean 2001, Vista was 2006.. > > I'm assuming that Windows is using ACPI reset these days, so presumably > that's what we should be doing by default, and blacklisting machines > where that doesn't work, rather than the reverse.. Using a DMI cutoff year in the mid-2000's seems like it would make sense. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Matthew Garrett on 6 Jan 2010 09:40 On Mon, Jan 04, 2010 at 05:45:58PM -0800, Arjan van de Ven wrote: > can we do it based on the dmi/acpi year? > Eg for all 2008 and later machines or something, while leaving the > older ones as is I think a saner model would be to use a similar method to Windows - that is, change behaviour based on the OSI calls that the firmware makes. If the firmware supports Vista, it's probably safe to use the ACPI reboot method. -- Matthew Garrett | mjg59(a)srcf.ucam.org -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Alan Cox on 6 Jan 2010 09:50 > KBD is present on all PCs, not so with acpi. If machine can't handle > kbd reboot, it is not IBM PC compatible. Most modern PC systems are not "IBM PC compatible" in various respects. Defaulting to ACPI reboot is fine as it can fall back to non ACPI reboot if there is no ACPI or ACPI doesn't provide the needed info for the system in question -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Pavel Machek on 6 Jan 2010 09:50 > commit 2cb758c617833c18c533e1c4c31167e59d092235 > Author: Len Brown <len.brown(a)intel.com> > Date: Thu Nov 6 22:43:21 2008 -0500 > > x86, ACPI: default to reboot via ACPI (again) > > We've run into systems which do not reboot properly > without using the ACPI reset mechanism. So lets > try this in linux-next for a while and see > how many existing machines stop rebooting > because they can't handle ACPI reboot. > Signed-off-by: Len Brown <len.brown(a)intel.com> Nak. > @@ -32,7 +32,7 @@ EXPORT_SYMBOL(pm_power_off); > > static const struct desc_ptr no_idt = {}; > static int reboot_mode; > -enum reboot_type reboot_type = BOOT_KBD; > +enum reboot_type reboot_type = BOOT_ACPI; > int reboot_force; > KBD is present on all PCs, not so with acpi. If machine can't handle kbd reboot, it is not IBM PC compatible. Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Len Brown on 6 Jan 2010 14:30
> > can we do it based on the dmi/acpi year? > I think a saner model would be to use a similar method to Windows - > that is, change behaviour based on the OSI calls that the firmware > makes. If the firmware supports Vista, it's probably safe to use the > ACPI reboot method. Andrey Borzenkov's Toshiba Portege 4000 failed to reset with ACPI, which is why we reverted ACPI reset as default in 2008. Toshiba shipped the Portege 4000 in 2002 running with Windows 2000, suggesting that Windows 2000 does not use ACPI reset -- at least not always. When debugging the reset failure in: http://bugzilla.kernel.org/show_bug.cgi?id=11942 Yakui Zhao found that Windows XP writes the ACPI reset register no matter if the FADT says it is valid or not: http://lkml.indiana.edu/hypermail/linux/kernel/0811.0/02272.html At the end of the day, we decided that Linux should honor that bit, but what we learned is that Windows XP apparently uses ACPI reset by default. So it is likely that our DMI exception lists will be minimized by using legacy reset for W2K generation and before; and using ACPI reset for Windows XP generation and after. As Robert Hancock corrected me, XP is _OSI(Windows 2001). But... using _OSI is not "a similar method to Windows". The BIOS does not need to invoke _OSI to determine if it should expose a properly functioning ACPI reset or not. Windows XP simply demanded it, and the box failed WHQL if it did not work. Further, there is no _guarantee_ that a BIOS will invoke _OSI at all, let alone a _rule_ for what _OSI() strings the BIOS will choose to query to trigger its Windows specific compatibility hooks -- even if common practice is for a desktop BIOS to evaluate _OSI strings in sequence up throught he most recent version of Windows it knows about... So I'm more comfortable with DMI, and any year after Windows 2000 is gone is probably reasonable, say 2003. I have no doubt that no matter what we do, we will end up with some exceptions on a blacklist, the goal is simply to minimize those lists. cheers, Len Brown, Intel Open Source Technology Center ps. For CONFIG_ACPI_BLACKLIST_YEAR we chose not to strive for consensus on a hard-coded year, but made it a config option. I'm not a fan of more config options, but that one allowed us to avoid thrashing about what year ACPI should kick in and defer that to the distros. I think it has probably served its purpose now, as Fedora for the last few years has shipped with this option disabled -- enabling ACPI on all systems that present an ACPI BIOS. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |