diff options
| -rw-r--r-- | drivers/acpi/acpica/utosi.c | 25 |
1 files changed, 25 insertions, 0 deletions
diff --git a/drivers/acpi/acpica/utosi.c b/drivers/acpi/acpica/utosi.c index 1e5525e87d34..685766fc6ca8 100644 --- a/drivers/acpi/acpica/utosi.c +++ b/drivers/acpi/acpica/utosi.c | |||
| @@ -47,6 +47,31 @@ | |||
| 47 | #define _COMPONENT ACPI_UTILITIES | 47 | #define _COMPONENT ACPI_UTILITIES |
| 48 | ACPI_MODULE_NAME("utosi") | 48 | ACPI_MODULE_NAME("utosi") |
| 49 | 49 | ||
| 50 | /****************************************************************************** | ||
| 51 | * | ||
| 52 | * ACPICA policy for new _OSI strings: | ||
| 53 | * | ||
| 54 | * It is the stated policy of ACPICA that new _OSI strings will be integrated | ||
| 55 | * into this module as soon as possible after they are defined. It is strongly | ||
| 56 | * recommended that all ACPICA hosts mirror this policy and integrate any | ||
| 57 | * changes to this module as soon as possible. There are several historical | ||
| 58 | * reasons behind this policy: | ||
| 59 | * | ||
| 60 | * 1) New BIOSs tend to test only the case where the host responds TRUE to | ||
| 61 | * the latest version of Windows, which would respond to the latest/newest | ||
| 62 | * _OSI string. Not responding TRUE to the latest version of Windows will | ||
| 63 | * risk executing untested code paths throughout the DSDT and SSDTs. | ||
| 64 | * | ||
| 65 | * 2) If a new _OSI string is recognized only after a significant delay, this | ||
| 66 | * has the potential to cause problems on existing working machines because | ||
| 67 | * of the possibility that a new and different path through the ASL code | ||
| 68 | * will be executed. | ||
| 69 | * | ||
| 70 | * 3) New _OSI strings are tending to come out about once per year. A delay | ||
| 71 | * in recognizing a new string for a significant amount of time risks the | ||
| 72 | * release of another string which only compounds the initial problem. | ||
| 73 | * | ||
| 74 | *****************************************************************************/ | ||
| 50 | /* | 75 | /* |
| 51 | * Strings supported by the _OSI predefined control method (which is | 76 | * Strings supported by the _OSI predefined control method (which is |
| 52 | * implemented internally within this module.) | 77 | * implemented internally within this module.) |
