From 759776ec7631665438dbf5880337144e265d1060 Mon Sep 17 00:00:00 2001 From: Jonathan Gray Date: Mon, 21 Jan 2008 12:43:10 +0000 Subject: Check against RESET_REG_SUP in FADT before doing the acpi reset dance after all, not doing so appears to break more machines than it fixes. ok marco@ --- sys/dev/acpi/acpi.c | 10 +++++++--- 1 file changed, 7 insertions(+), 3 deletions(-) (limited to 'sys') diff --git a/sys/dev/acpi/acpi.c b/sys/dev/acpi/acpi.c index fcab2fefb15..a81dbbc553e 100644 --- a/sys/dev/acpi/acpi.c +++ b/sys/dev/acpi/acpi.c @@ -1,4 +1,4 @@ -/* $OpenBSD: acpi.c,v 1.112 2008/01/05 18:26:30 kettenis Exp $ */ +/* $OpenBSD: acpi.c,v 1.113 2008/01/21 12:43:09 jsg Exp $ */ /* * Copyright (c) 2005 Thorsten Lockert * Copyright (c) 2005 Jordan Hargrave @@ -1195,8 +1195,12 @@ acpi_reset(void) fadt = acpi_softc->sc_fadt; - /* FADT_RESET_REG_SUP is not properly set in some implementations */ - if (acpi_softc->sc_revision <= 1 || fadt->reset_reg.address == 0) + /* + * RESET_REG_SUP is not properly set in some implementations, + * but not testing against it breaks more machines than it fixes + */ + if (acpi_softc->sc_revision <= 1 || + !(fadt->flags & FADT_RESET_REG_SUP) || fadt->reset_reg.address == 0) return; value = fadt->reset_value; -- cgit v1.2.3