From: Jan Rychter <jan-JAsPCFd0eodBDgjK7y7TUQ@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: BUG: power button doesn't generate events
Date: Wed, 06 Aug 2003 19:56:43 -0700 [thread overview]
Message-ID: <m2smoep444.fsf@tnuctip.rychter.com> (raw)
In-Reply-To: F760B14C9561B941B89469F59BA3A8470255EEA7@orsmsx401.jf.intel.com
[-- Attachment #1: Type: text/plain, Size: 1038 bytes --]
>> From: Jan Rychter [mailto:jan-JAsPCFd0eodBDgjK7y7TUQ@public.gmane.org] I get LID button events
>> fine, but the power button doesn't seem to generate any events
>>
>> Does the following bit of DSDT mean the power button should generate
>> events?
>>
>> Device (PWRB) { Name (_HID, EisaId ("PNP0C0C")) Name (_PRW, Package
>> (0x02) { 0x08, 0x04 }) Name (_STA, 0x0B)
>> }
Andrew> ACPI: Power Button (FF) [PWRF]
Andrew> It looks like it is finding a fixed-feature power button before
Andrew> the control method power button, and therefore the CM power
Andrew> button isn't being set up. So this raises in my mind 2
Andrew> questions:
Andrew> 1) Why isn't the FF power button working?
Andrew> 2) On a system with both, is the current behavior (favor FF
Andrew> over CM) the
Andrew> proper behavior?
I hope these questions weren't addressed to me, because I certainly
can't answer them. I just thought a bug report might be useful. And I'd
like my power button to work some day :-)
--J.
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2003-08-07 2:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-25 20:14 BUG: power button doesn't generate events Grover, Andrew
2003-08-07 2:56 ` Jan Rychter [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-08 8:32 Yu, Luming
2003-07-20 18:39 Jan Rychter
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=m2smoep444.fsf@tnuctip.rychter.com \
--to=jan-jaspcfd0eodbdgjk7y7tuq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox