27.10.2015 Views

Advanced Configuration and Power Interface Specification

ACPI_6.0

ACPI_6.0

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

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

with devices defined herein. It further reserves all strings representing 4 HEX digits for<br />

exclusive use with PCI-assigned Vendor IDs.<br />

Example ASL:<br />

Name (_HID, EISAID ("PNP0C0C"))<br />

Name (_HID, EISAID ("INT0800"))<br />

Name (_HID, "ACPI0003")<br />

Name (_HID, "MSFT0003")<br />

Name (_HID, "80860003")<br />

// Control-Method <strong>Power</strong> Button<br />

// Firmware Hub<br />

// AC adapter device<br />

// Vendor-defined device<br />

// PCI-assigned device identifier<br />

6.1.6 _HRV (Hardware Revision)<br />

This object is used to supply OSPM with the device’s hardware revision. The use of _HRV is<br />

optional.<br />

Arguments:<br />

None<br />

Return Value:<br />

An Integer (DWORD) containing the hardware revision number<br />

Example ASL:<br />

Name (_HRV, 0x0003)// Revision number 3 of this hardware device<br />

6.1.7 _MLS (Multiple Language String)<br />

The _MLS object provides OSPM a human readable description of a device in multiple languages.<br />

This information may be provided to the end user when the OSPM is unable to get any other<br />

information about this device. Although this functionality is also provided by the _STR object,<br />

_MLS exp<strong>and</strong>s that functionality <strong>and</strong> provides vendors with the capability to provide multiple<br />

strings in multiple languages. The _MLS object evaluates to a package of packages. Each subpackage<br />

consists of a Language identifier <strong>and</strong> corresponding unicode string for a given locale.<br />

Specifying a language identifier allows OSPM to easily determine if support for displaying the<br />

Unicode string is available. OSPM can use this information to determine whether or not to display<br />

the device string, or which string is appropriate for a user’s preferred locale.<br />

It is assumed that OSPM will always support the primary English locale to accommodate English<br />

embedded in a non-English string, such as a br<strong>and</strong> name.<br />

If OSPM doesn’t support the specific sub-language ID it may choose to use the primary language ID<br />

for displaying device text.<br />

Arguments:<br />

None<br />

Return Value:<br />

A variable-length Package containing a list of language descriptor Packages as described below.<br />

282 April, 2015 Version 6.0

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

Saved successfully!

Ooh no, something went wrong!