18.12.2012 Views

Advanced Configuration and Power Interface Specification

Advanced Configuration and Power Interface Specification

Advanced Configuration and Power Interface Specification

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 />

5.2.10 Firmware ACPI Control Structure (FACS)<br />

The Firmware ACPI Control Structure (FACS) is a structure in read/write memory that the BIOS<br />

reserves for ACPI usage. This structure is passed to an ACPI-compatible OS using the FADT. For<br />

more information about the FADT FIRMWARE_CTRL field, see Table 5.2.9, “Fixed ACPI<br />

Description Table (FADT).”<br />

The BIOS aligns the FACS on a 64-byte boundary anywhere within the system’s memory address<br />

space. The memory where the FACS structure resides must not be reported as system<br />

AddressRangeMemory in the system address map. For example, the E820 address map reporting<br />

interface would report the region as AddressRangeReserved. For more information about system<br />

address map reporting interfaces, see Section 15, “System Address Map <strong>Interface</strong>s.”<br />

Table 5-37 Firmware ACPI Control Structure (FACS)<br />

Byte Byte<br />

Field<br />

Length Offset Description<br />

Signature 4 0 ‘FACS’<br />

Length 4 4 Length, in bytes, of the entire Firmware ACPI Control Structure.<br />

This value is 64 bytes or larger.<br />

Hardware Signature 4 8 The value of the system’s “hardware signature” at last boot.<br />

This value is calculated by the BIOS on a best effort basis to<br />

indicate the base hardware configuration of the system such<br />

that different base hardware configurations can have different<br />

hardware signature values. OSPM uses this information in<br />

waking from an S4 state, by comparing the current hardware<br />

signature to the signature values saved in the non-volatile sleep<br />

image. If the values are not the same, OSPM assumes that the<br />

saved non-volatile image is from a different hardware<br />

configuration <strong>and</strong> cannot be restored.<br />

Hewlett-Packard/Intel/Microsoft/Phoenix/Toshiba 127

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

Saved successfully!

Ooh no, something went wrong!