UEFI Forum releases the UEFI 2.10 specification and the ACPI 6.5 specification
Beaverton, United States – The UEFI Forum announced the release of the unified extensible firmware interface (UEFI) 2.10 specification and advanced configuration and power interface (ACPI) 6.5 specification. The new specification versions expand support for new processor types, memory interfaces and platform types, while allowing for crypto agility in post-quantum system security.
UEFI 2.10 specification highlights:
- Introducing UEFI Conformance Profiles, allowing support for more types of platforms and implementation codebases
- Crypto agility including SHA-384/SHA-512 signing scheme for authenticated variables support
- Emerging LoongArch and RISC-V processor architecture support
- Add confidential computing extension
“We are excited to share the new Conformance Profiles feature, responsive to community pull for a way to make the UEFI Forum’s work useful,” says Mark Doran, UEFI Forum president. “The conformance profiles feature will expand the platform types UEFI can support to an ever wider range of platform types like IoT, embedded and automotive spaces – beyond general purpose computers.”
ACPI 6.5 specification highlights:
- CXL memory support
- LoongArch processor architecture support
- Confidential computing event log support
- USB-C USB4 support
The ACPI 6.5 specification update contains the most changes ever made using the “Code First” process of the UEFI Forum. This process acknowledges the valuable insights and contributions of open-source communities to the development of the specifications maintained by the UEFI Forum and allows non-members a path to contribute to the specifications.
To learn more, access the UEFI 2.10 specification and the ACPI 6.5 specification on the UEFI Forum specification webpage. The UEFI specification 2.9 errata A and ACPI specification 6.4 errata A are also available on the specifications page.
Read the white paper UEFI conformance profiles: Allowing “Reduced Model” implementations to learn more about the new conformance profiles feature.
Comment on this article below or via Twitter @IoTGN