From: Alexey Starikovskiy <alexey.y.starikovskiy@linux.intel.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Help with ACPI events
Date: Fri, 29 Dec 2006 13:46:12 +0300 [thread overview]
Message-ID: <4594F1F4.9080102@linux.intel.com> (raw)
In-Reply-To: <45947B98.5050309@lwfinger.net>
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@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2006-12-29 10:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-29 2:21 Help with ACPI events Larry Finger
2006-12-29 10:46 ` Alexey Starikovskiy [this message]
2006-12-30 1:28 ` Larry Finger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4594F1F4.9080102@linux.intel.com \
--to=alexey.y.starikovskiy@linux.intel.com \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-acpi@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.