If this flag is set, the platform must implement the ACPI Time and Alarm Control Method device. The "IA-PC Boot Architecture Flags" field (offset 109) has a new "CMOS RTC Not Present" flag (bit offset 5) to indicate that the PC's CMOS RTC is either not implemented, or does not exist at the legacy addresses. This role influences power management policy for the display and input, and affects the display of on-screen keyboards. The FADT Preferred_PM_Profile field (byte offset 45) has a new role entry, "Tablet".
#Dsdt windows extract windows
If this flag is set, Windows will not try to sleep and resume, but will instead use platform idle states and connected standby. Indicates that the platform supports low-power idle states within the ACPI S0 system power state that are more energy efficient than any Sx sleep state. This flag must be set if the ACPI Fixed Hardware Programming Model is not implemented.īit offset 21. Indicates that ACPI hardware is not available on this platform. The Flags field within the FADT (offset 112) has two new flags:īit offset 20. To support hardware-reduced ACPI platforms, ACPI 5.0 extends the FADT table definition as follows: The Fixed ACPI Hardware Table (FADT) contains important information about the various Fixed Hardware features available on the platform. Optionally, additional system description tables (SSDT) The Firmware Performance Data Table (FPDT) Optionally, the Core System Resource Table (CSRT) The multiple interrupt controller table (MADT) Specifically, this table contains pointers to the following: The RSDT (or XSDT) includes pointers to any other system description tables provided on the platform. (If both table addresses are provided, Windows will prefer the XSDT.) Root System Description Table (RSDT) The platform firmware fills in the address of either the RSDT or XSDT in the RSDP. Hence, Windows will use the EFI system table to locate the RSDP, as described in section 5.2.5.2, "Finding the RSDP on UEFI Enabled Systems", of the ACPI 5.0 specification. Windows depends on UEFI firmware to boot up the hardware platform.
#Dsdt windows extract software
This software can therefore be written once, thoroughly tested, and then optimized over time. With the table strategy, the platform-variable attributes of a particular platform are provided in a table, and used by generic software to adapt itself to the specific set of IP blocks integrated into the platform. The idea behind these tables is to enable generic software to support standard intellectual property (IP) blocks that can be integrated into various platforms in diverse ways. Windows utilizes this table-passing mechanism, in addition to the specific tables that are described in this article. Table structures and headers, including ID and checksum fields, are defined in the ACPI 5.0 specification.
#Dsdt windows extract plus
ACPI defines a generic, extensible table-passing mechanism, plus specific tables for describing the platform to the operating system. Implementation of the Advanced Configuration and Power Interface (ACPI) Hardware Specification is not required on SoC-based platforms, but much of the ACPI Software Specification is (or can be) required.