[PATCH] ACPI patches updated

Grover, Andrew (andrew.grover@intel.com)
Fri, 1 Nov 2002 14:33:33 -0800


Hi all,

ACPI patches dated 20021101 is now released at http://sf.net/projects/acpi
<http://sf.net/projects/acpi> for both 2.4.x and 2.5.x. It includes a fix
for a bug causing processor and thermal drivers to fail to load, as well as
a few others.

Thanks -- Regards -- Andy

----------------------------------------
01 November 2002. Summary of changes for version 20021101.

1) Linux

Fixed a problem introduced in the previous release where the
Processor and Thermal objects were not recognized and
installed in /proc. This was related to the scope type change
described below.

2) ACPI CA Core Subsystem:

Fixed a problem where platforms that have a GPE1 block but no
GPE0 block were not handled correctly. This resulted in a
"GPE overlap" error message. GPE0 is no longer required.

Removed code added in the previous release that inserted nodes
into the namespace in alphabetical order. This caused some
side-effects on various machines. The root cause of the
problem is still under investigation since in theory, the
internal ordering of the namespace nodes should not matter.

Enhanced error reporting for the case where a named object is
not found during control method execution. The full ACPI
namepath (name reference) of the object that was not found is
displayed in this case.

Note: as a result of the overhaul of the namespace object
types in the previous release, the namespace nodes for the
predefined scopes (_TZ, _PR, etc.) are now of the type
ACPI_TYPE_LOCAL_SCOPE instead of ACPI_TYPE_ANY. This
simplifies the namespace management code but may affect code
that walks the namespace tree looking for specific object
types.

-----------------------------
Andrew Grover
Intel Labs / Mobile Architecture
andrew.grover@intel.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/