This specification describes a format for storing ACPI tables in an implementation of the Intel® Platform Innovation Framework for EFI (hereafter referred to as the "Framework"). The Advanced Configuration and Power Interface Specification (hereafter referred to as the "ACPI specification") defines a set of tables that describe platform configuration and power management. The platform Driver Execution Environment (DXE) driver must provide these tables to the operating system. These tables are largely static in nature and platform specific. This specification does the following: • Describes the basic components of ACPI table storage• Provides code definitions for ACPI table storage that are architecturally required by the Intel® Platform Innovation Framework for EFI Architecture Specification

See Industry Specifications in the Framework master help system for the URL for the ACPI specification.

Scope: This specification provides a design for storing ACPI tables that comply with the ACPI specification, revisions 1.0b and 2.0, in a Framework-compliant firmware device. This method relies on existing firmware volume (FV) and Firmware File System (FFS) designs. See the following specifications for more information on FV and FFS designs: • Intel® Platform Innovation Framework for EFI Firmware Volume Specification• Intel® Platform Innovation Framework for EFI Firmware File System Specification

Data Structure Descriptions: Intel® processors based on 32-bit Intel® architecture (IA-32) are “little endian” machines. This distinction means that the low-order byte of a multibyte data item in memory is at the lowest address, while the high-order byte is at the highest address. Processors of the Intel® Itanium® processor family may be configured for both “little endian” and “big endian” operation. All implementations designed to conform to this specification will use “little endian” operation. In some memory layout descriptions, certain fields are marked reserved. Software must initialize such fields to zero and ignore them when read. On an update operation, software must preserve any reserved field.

This specification describes a format for storing ACPI tables in an implementation of the Intel® Platform Innovation Framework for EFI (hereafter referred to as the "Framework"). The Advanced Configuration and Power Interface Specification (hereafter referred to as the "ACPI specification") defines a set of tables that describe platform configuration and power management. The platform Driver Execution Environment (DXE) driver must provide these tables to the operating system. These tables are largely static in nature and platform specific. This specification does the following: • Describes the basic components of ACPI table storage• Provides code definitions for ACPI table storage that are architecturally required by the Intel® Platform Innovation Framework for EFI Architecture Specification

See Industry Specifications in the Framework master help system for the URL for the ACPI specification.

Scope: This specification provides a design for storing ACPI tables that comply with the ACPI specification, revisions 1.0b and 2.0, in a Framework-compliant firmware device. This method relies on existing firmware volume (FV) and Firmware File System (FFS) designs. See the following specifications for more information on FV and FFS designs: • Intel® Platform Innovation Framework for EFI Firmware Volume Specification• Intel® Platform Innovation Framework for EFI Firmware File System Specification

Data Structure Descriptions: Intel® processors based on 32-bit Intel® architecture (IA-32) are “little endian” machines. This distinction means that the low-order byte of a multibyte data item in memory is at the lowest address, while the high-order byte is at the highest address. Processors of the Intel® Itanium® processor family may be configured for both “little endian” and “big endian” operation. All implementations designed to conform to this specification will use “little endian” operation. In some memory layout descriptions, certain fields are marked reserved. Software must initialize such fields to zero and ignore them when read. On an update operation, software must preserve any reserved field.