Disable serialize_methods and enable _OSI support by default. The former

is necessary because some IBMs use recursive methods (pointed out by
Robert Moore from Intel).  The latter was a typo on my part.  It was disabled
by default when it should have been enabled.
This commit is contained in:
Nate Lawson 2004-03-30 07:35:18 +00:00
parent 32d9553d83
commit c9b8d77d80
Notes: svn2git 2020-12-20 02:59:44 +00:00
svn path=/head/; revision=127609

View File

@ -235,14 +235,23 @@ SYSCTL_STRING(_debug_acpi, OID_AUTO, acpi_ca_version, CTLFLAG_RD,
/*
* Allow override of whether methods execute in parallel or not.
* Default to serial behavior as this fixes some AE_ALREADY_EXISTS errors
* and matches the MS interpreter.
* Enable this for serial behavior, which fixes "AE_ALREADY_EXISTS"
* errors for AML that really can't handle parallel method execution.
* It is off by default since this breaks recursive methods and
* some IBMs use such code.
*/
static int acpi_serialize_methods = 1;
static int acpi_serialize_methods;
TUNABLE_INT("hw.acpi.serialize_methods", &acpi_serialize_methods);
/* Allow override of whether to support the _OSI method. */
static int acpi_osi_method;
/*
* Allow override of whether to support the _OSI method. This allows us
* to claim compatibility with various MS OSs without changing the value
* we report for _OS. This is enabled by default since it fixes some
* problems with interrupt routing although it can be disabled if it
* causes problems. See the definition of "AcpiGbl_ValidOsiStrings" for
* a list of systems we claim.
*/
static int acpi_osi_method = 1;
TUNABLE_INT("hw.acpi.osi_method", &acpi_osi_method);
/*