On Wed, Jan 06, 2010 at 02:26:44PM -0500, Len Brown wrote: > 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. http://download.microsoft.com/download/7/E/7/7E7662CF-CBEA-470B-A97E-CE7CE0D98DC2/WinACPI_OSI.docx was what I was referring to: "By using the _OSI method, ASL writers can easily determine the version of the ACPI interfaces that the host operating system supports. This versioning method provides a solution for creating firmware that can support future operating systems and enable the operating system to change behavior based on the requested interface levels." We know that this is used for deciding whether or not to block system IO accesses, but it wouldn't surprise me if it's also used to determine other functionality like whether or not the ACPI interface is used for rebooting. > 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... It's effectively guaranteed if the system is validated with Windows. -- Matthew Garrett | mjg59@xxxxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
