[PATCH] [0/2] acpiphp extension for 2.6.7 (take 3)

From: Vernon Mauery
Date: Fri Jul 02 2004 - 19:04:19 EST


On Fri, 2004-07-02 at 13:58, Greg KH wrote:
> I'm going to hold off applying these till you address the issues raised
> on the mailing list.

Greg,

I think I have fixed the problems that have been discussed on the
lists. Many of the fixes had to do with too many checks on pointers. I
killed all the checks except for the ones that would make the machine
oops immediately. That was the guideline I used to make the decision on
what was a worthy check or not. Let me know what you think about the
new version

Just for good measure, the description is included below again. :)

The two patches are to follow

--Vernon


After much discussion, dissection, rewriting and reading (documentation
of course), I finally think this patch is ready to be included in the
kernel. I have chosen to split it into 2 parts because really, that's
what it is -- a patch to acpiphp that allows other modules to register
attention LED callback functions and also a new module that does just
that for the IBM ACPI systems. These patches were made against the
2.6.7 kernel tree.

01 - acpiphp-attention-v0.1d.patch

This patch adds the ability to register callback functions with
the acpiphp core to set and get the current attention LED
status. The reason this is needed is because there is not set
ACPI standard for how this is done so each hardware platform may
implement it differently. To keep hardware specific code out of
acpiphp, we allow other modules to register their code with it.


02 - acpiphp_ibm-v1.0.1d.patch

This patch adds the first driver that actually uses the callback
function for attention LEDs that the acpiphp-attention patch
adds. It searches the ACPI namespace for IBM hardware, sets up
the callbacks and sets up a handler to read ACPI events and
forward them on to /proc/acpi/event. It also exports an ACPI
table that shows current hotplug status to userland.


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