Home / acpi-patch / Latest
Name Modified Size Downloads / Week Status
Parent folder
Totals: 1 Item   3.1 kB 1
README.ACPI 2003-10-06 3.1 kB 11 weekly downloads
The Linux Kernel ACPI Patch is published both as "BK trees" on bkbits.net, and as plain patches on kernel.org. Upon updates, e-mail is sent to acpi-devel@lists.sourceforge.net The patches themselves are no longer distributed from sourceforge.net BK Trees: http://linux-acpi.bkbits.net/ There are two flavors -- test and release. The latest code is in the test trees. When it has seen some airtime, the test trees are pulled into the release trees, which are a staging area for pulling into the baseline kernels. There are currently three releases: 2.4.22 is based on (frozen) v2.4.22 2.4.23 is based on (recent) 2.4.23 from http://linux.bkbits.net/linux-2.4 2.6.0 is based on (recent) 2.6.0 from http://linux.bkbits.net/linux-2.5 (Two flavors) x (3 releases) = 6 trees: http://linux-acpi.bkbits.net/linux-acpi-test-2.4.22 http://linux-acpi.bkbits.net/linux-acpi-test-2.4.23 http://linux-acpi.bkbits.net/linux-acpi-test-2.6.0 http://linux-acpi.bkbits.net/linux-acpi-release-2.4.22 http://linux-acpi.bkbits.net/linux-acpi-release-2.4.23 http://linux-acpi.bkbits.net/linux-acpi-release-2.6.0 The easiest way to get a copy of the latest ACPI patch and keep it up to date is to snag a (free) copy of bitkeeper from http://bitkeeper.com Choose the flavor and release from above, clone it onto your drive: $ bk clone http://linux-acpi.bkbits.net/linux-acpi-test-2.4.22 my-acpi-repo See if new updates are available: $ cd my-acpi-repo $ bk changes -R pull updates: $ cd my-acpi-repo $ bk pull Note that the pull will refuse to update if it discovers that you checked out files for editing that it needs to change. So if you make local changes, you may want to "bk clone" your acpi repository to a place where you make changes, or "bk export" the SCCS tree to a plain source tree for modification. You can also browse the source trees and csets on bkbits.net. Note that it is easier to see the ACPI-specific csets by browsing the "frozen" tree because only ACPI-specific csets are checked in on top of the frozen kernel baseline. Plain Patches: ftp://ftp.kernel.org/pub/linux/kernel/people/lenb/acpi/patches For the 2.4.22 and 2.6.0 test trees, individual patches are available for each cset. These patches will stick around at least until they're integrated into the baseline kernel. The patch filenames begin with a date-timestamp; and should be applied in date-timestamp order in case they depend on each other. For the 2.4.22, 2.4.23, and 2.6.0 release trees, patches that bundle groups of csets together are available. The ACPI version number is generally incremented for each bundle, and appears in the patch filename along with the name of the release the patch applies to. In both cases, there is a header at the top of the patch including the BK cset comments to describe what is included in the patch. Note you can test if a patch will apply cleanly before you apply it for real: $ cd my-src/linux/ To test $ patch --dry-run -Np1 < acpi.patch For real: $ patch -Np1 < acpi.patch Questsion, comments, suggestions to len.brown @ intel.com Thanks, -Len 2003/9/23
Source: README.ACPI, updated 2003-10-06