Next, you should look into your DSDT and find what exactly _Q10 does (it
might set/reset some variable with descriptive name). Then, in your code
you can read the state of this variable with
acpi_evaluate_integer/acpi_evaluate_object. Please look at drivers in
drivers/acpi for examples.
Regards,
Alex.
Larry Finger wrote:
I'm writing for some help with ACPI events, which may be getting in the way of the setting of LEDs
for the bcm43xx module. I have an HP notebook with a "Broadcom Corporation Dell Wireless 1390 WLAN
Mini-PCI Card". This machine has a wireless on/off switch on the front. By experimenting while using
2.6.9.1, I found the necessary code needed to toggle the LED associated with the switch. The same
code does not work with 2.6.20-rc2 and the LED is always off. The state of the switch is correctly
read out by my code, but no deal with changing the LED state.
The reason I'm writing you is that whenever the switch is changed on 2.6.20, a "ACPI: EC: evaluating
_Q10" message is logged just before my code detects the switch change. I looked at the acpi driver a
little, but quickly got lost.
Is there a change in the acpi subsystem in 2.6.20 that might be interfering? Where should I look next?
Thanks,
Larry
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
