27.10.2015 Views

Advanced Configuration and Power Interface Specification

ACPI_6.0

ACPI_6.0

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Advanced</strong> <strong>Configuration</strong> <strong>and</strong> <strong>Power</strong> <strong>Interface</strong> <strong>Specification</strong><br />

The _OSI method has one argument <strong>and</strong> one return value. The argument is an OS vendor defined<br />

string representing a set of OS interfaces <strong>and</strong> behaviors or an ACPI defined string representing an<br />

operating system <strong>and</strong> an ACPI feature group of the form, “OSVendorString-FeatureGroupString”.<br />

Arguments: (1)<br />

Arg0 – A String containing the OS interface / behavior compatibility string or the Feature Group<br />

string, as defined in Table 5-165, or the “OS Vendor String Prefix – OS Vendor Specific String”. OS<br />

Vendor String Prefixes are defined inTable 5-164<br />

Return Value:<br />

An Integer containing a Boolean that indicates whether the requested feature is supported:<br />

0x0 –<br />

0xFFFFFFFF –<br />

The interface, behavior, or feature is not supported<br />

The interface, behavior, or feature is supported<br />

OSPM may indicate support for multiple OS interface / behavior strings if the operating system<br />

supports the behaviors. For example, a newer version of an operating system may indicate support<br />

for strings from all or some of the prior versions of that operating system.<br />

_OSI provides the platform with the ability to support new operating system versions <strong>and</strong> their<br />

associated features when they become available. OSPM can choose to expose new functionality<br />

based on the _OSI argument string. That is, OSPM can use the strings passed into _OSI to ensure<br />

compatibility between older platforms <strong>and</strong> newer operating systems by maintaining known<br />

compatible behavior for a platform. As such, it is recommended that _OSI be evaluated by the<br />

\_SB.INI control method so that platform compatible behavior or features are available early in<br />

operating system initialization.<br />

Since feature group functionality may be dependent on OSPM implementation, it may be required<br />

that OS vendor-defined strings be checked before feature group strings.<br />

Platform developers should consult OS vendor specific information for OS vendor defined strings<br />

representing a set of OS interfaces <strong>and</strong> behaviors. ACPI defined strings representing an operating<br />

system <strong>and</strong> an ACPI feature group are listed in the following tables.<br />

Table 5-164 Operating System Vendor Strings<br />

Operating System Vendor String Prefix<br />

“FreeBSD”<br />

“HP-UX”<br />

Description<br />

Free BSD<br />

HP Unix Operating Environment<br />

“Linux”<br />

“OpenVMS”<br />

“Windows”<br />

GNU/Linux Operating system<br />

HP OpenVMS Operating Environment<br />

Microsoft Windows<br />

Table 5-165 Feature Group Strings<br />

Feature Group String<br />

“Module Device”<br />

Description<br />

OSPM supports the declaration of module device (ACPI0004) in the<br />

namespace <strong>and</strong> will enumerate objects under the module device scope.<br />

270 April, 2015 Version 6.0

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!