The ACPI Component Architecture (ACPICA) project provides an operating system (OS)-independent reference implementation of the Advanced Configuration and Power Interface Specification (ACPI). It can be easily adapted to execute under any host OS. The ACPICA code is meant to be directly integrated into the host OS as a kernel-resident subsystem. Hosting the ACPICA subsystem requires no changes to the core ACPICA code. Instead, a small OS-specific interface layer is written specifically for each host OS in order to interface the ACPICA code to the native OS services.


The complexity of the ACPI specification leads to a lengthy and difficult implementation in operating system software. The primary purpose of the ACPI Component Architecture is to simplify ACPI implementations for operating system vendors (OSVs) by providing major portions of an ACPI implementation in OS-independent ACPI modules that can be easily integrated into any OS.

Recent News

  • AcpiExec supports full history and line-editing on unix systems, in version 20130927. - 27 September, 2013 - 09:55
  • Document "Runtime BIOS Fixups for ACPI Tables" is posted - 25 July, 2013 - 09:08
  • AcpiDump is now supported on FreeBSD, Linux, and Windows in version 20130626. - 26 June, 2013 - 11:56
  • A portable AcpiDump utility has been released in version 20130517. - 17 May, 2013 - 09:30
  • The entire ACPICA website has been reimplemented and upgraded - 4 April, 2013 - 08:11
  • The ACPICA bugzilla has been moved to https://bugs.acpica.org. - 4 April, 2013 - 07:49
  • The ACPICA git source repository has been moved to: github.com/acpica/acpica.git - 7 March, 2013 - 08:59
  • The entire acpica.org website was moved to https (including the bugzilla). - 10 May, 2012 - 08:58
  • Initial implementation of the iASL preprocessor released in version 20120320. - 20 March, 2012 - 08:58
  • Full support for ACPI 5.0 in ACPICA is released (version 20111123). - 23 November, 2011 - 08:57