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.

ACPI Software Programming Model<br />

OEM Table ID 8 16 An OEM-supplied string that the OEM uses to identify the particular<br />

data table. This field is particularly useful when defining a definition<br />

block to distinguish definition block functions. The OEM assigns<br />

each dissimilar table a new OEM Table ID.<br />

OEM Revision 4 24 An OEM-supplied revision number. Larger numbers are assumed to<br />

be newer revisions.<br />

Creator ID 4 28 Vendor ID of utility that created the table. For tables containing<br />

Definition Blocks, this is the ID for the ASL Compiler.<br />

Creator Revision 4 32 Revision of utility that created the table. For tables containing<br />

Definition Blocks, this is the revision for the ASL Compiler.<br />

For OEMs, good design practices will ensure consistency when assigning OEMID <strong>and</strong> OEM Table<br />

ID fields in any table. The intent of these fields is to allow for a binary control system that support<br />

services can use. Because many support functions can be automated, it is useful when a tool can<br />

programmatically determine which table release is a compatible <strong>and</strong> more recent revision of a prior<br />

table on the same OEMID <strong>and</strong> OEM Table ID.<br />

Table 5-30 <strong>and</strong> Table 5-31 contain the system description table signatures defined by this<br />

specification. These system description tables may be defined by ACPI <strong>and</strong> documented within this<br />

specification (Table 5-30) or they may be simply reserved by ACPI <strong>and</strong> defined by other industry<br />

specifications (Table 5-31). This allows OS <strong>and</strong> platform specific tables to be defined <strong>and</strong> pointed to<br />

by the RSDT/XSDT as needed. For tables defined by other industry specifications, the ACPI<br />

specification acts as gatekeeper to avoid collisions in table signatures.<br />

Table signatures will be reserved by the ACPI promoters <strong>and</strong> posted independently of this<br />

specification in ACPI errata <strong>and</strong> clarification documents on the ACPI web site. Requests to reserve a<br />

4-byte alphanumeric table signature should be sent to the email address info@acpi.info <strong>and</strong> should<br />

include the purpose of the table <strong>and</strong> reference URL to a document that describes the table format.<br />

Tables defined outside of the ACPI specification may define data value encodings in either little<br />

endian or big endian format. For the purpose of clarity, external table definition documents should<br />

include the endian-ness of their data value encodings.<br />

Since reference URLs can change over time <strong>and</strong> may not always be up-to-date in this specification, a<br />

separate document containing the latest known reference URLs can be found at “Links to ACPI-<br />

Related Documents” (http://uefi.org/acpi), which should conspicuously be placed in the same<br />

location as this specification.<br />

Table 5-30 DESCRIPTION_HEADER Signatures for tables defined by ACPI<br />

Signature Description Reference<br />

“APIC” Multiple APIC Description Table Section 5.2.12, “Multiple APIC Description Table”<br />

“BERT” Boot Error Record Table Section 18.3.1, “Boot Error Source”<br />

“BGRT” Boot Graphics Resource Table Section 5.2.22, “Boot Graphics Resource Table”<br />

“CPEP”<br />

“DSDT”<br />

Corrected Platform Error Polling<br />

Table<br />

Differentiated System Description<br />

Table<br />

Section 5.2.18, “Corrected Platform Error Polling Table”<br />

Section 5.2.11.1, “Differentiated System Description<br />

Table”<br />

Version 6.0 111

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

Saved successfully!

Ooh no, something went wrong!