Sorry, you need to enable JavaScript to visit this website.


This project enables Linux to take advantage of platforms supporting Advanced Configuration & Power Interface -- virtually all high-volume i386, x86_64, and ia64 systems since 1999. ACPI, known as a Hardware Abstraction Layer (HAL) in embedded computing, is an abstraction layer between the operating system, platform firmware and hardware. This allows the OS and the platform to evolve independently. The core of the Linux ACPI implementation comes from ACPICA (ACPI Component Architecture). ACPICA includes an ACPI Machine Language (AML) interpreter that is resident in the Linux kernel. Several other operating systems use the same ACPICA core interpreter, including BSD and OpenSolaris. ACPICA also comes with a simulator, test suites, and a compiler, to translate ACPI Source Language (ASL) into AML.

If you are unable to use git, you can apply the latest consolidated ACPI test branch using a plain patch:

This directory includes patches from the Linux/ACPI git release branch. Len publishes these when he sends a pull request to Linus. If Linus doesn't pull for awhile, this patch tells you what is waiting to go upstream. As soon as Linus pulls, however, this patch becomes a duplicate of what is in Linus' tree and, thus, no longer applies.

The patches are named like this:


The patch above:

  • was created on the release branch
  • was created sometime after 2.6.15-rc5
  • includes ACPICA, up through 20050902     

The directory above includes patches from the Linux_ACPI _test_test branch, as well as other topic branches, such as ACPICA, shown below:


Len rarely publishes individual test patches here, because they can now be pulled from the GUI using gitweb:

Patch Signing

Files on are compressed and signed, per

If you'd like to verify the signature, import the key by:
gpg --keyserver --recv-keys 0x517D0F0E verify integrity by:
gpg --verify you can skip <sigfile> if it is in the same directory as <sigfile>.

Applying Patches

Both test and release patches have a header at the top of the patch, including commit comments to describe what is included in the patch. Note that you can test whether a patch will apply cleanly before you actually apply it:

$ cd my-src/linux/

To test:
$ patch --dry-run -Np1 < acpi.patch

For real:
$ patch -Np1 < acpi.patch