From: Greg Sarjeant <greg-QNIYhHqVzB9kr2E5YSwMOQ@public.gmane.org>
To: Ducrot Bruno <ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
Cc: "Grover,
Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>,
acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Gateway 200X (again) - No power button events
Date: Wed, 21 Jan 2004 10:25:14 -0500 [thread overview]
Message-ID: <1074698713.5964.23.camel@localhost> (raw)
In-Reply-To: <20040121102356.GU25416-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
On Wed, 2004-01-21 at 05:23, Ducrot Bruno wrote:
> 1- At first, does this info file give accurate informations?
Yes. When it detects the FF power button, I have this:
type: Power Button (FF)
When I comment out those lines in scan.c to get the CM button, it reads:
type: Power Button (CM)
> 2- What happens if in one terminal you do something like
> watch -d 'cat /proc/interrupts'
> then press this button?
I tried this with the FF button. Interestingly, it does generate
interrupts when I press it (I unloaded all of the ACPI modules except
for button, so I imagine that this must be what caused the requests on
the acpi interrupt). So, I do get some sort of response from the system.
Should button.c acpi_button_notify_fixed() be called when I press the FF
button? It isn't currently.
> 3- also look into the ASL
> if you have some Notify(PWRF, ...), then try to insert some
> debug statements via Store ("PWRF notify xx", Debug) with
> xx being the number of the notify.
I don't have any Notify(PWRF, ...) methods in the ASL. They are all
Notify(PWRB, ...). When the system detects the FF button, it refers to
it as PWRF, and when it detects the CM button, it refers to it as PWRB.
In fact, the DSDT doesn't define a PWRF at all. I imagine that that is
specified in the FADT? As Andy said, the system disregards the CM button
entirely when it finds the FF button. I submitted a bug (1920), so
perhaps the behavior will change in the future. But I guess that that
contradicts the spec, so maybe not. I wouldn't want to break a bunch of
other machines just for the sake of a little convenience on my laptop :)
Perhaps the real problem is that the FF button isn't generating events?
Thanks,
Greg
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
next prev parent reply other threads:[~2004-01-21 15:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 20:15 Gateway 200X (again) - No power button events Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A84702C93238-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2004-01-20 20:17 ` Nate Lawson
2004-01-20 20:28 ` Greg Sarjeant
[not found] ` <1074630523.3313.17.camel-bi+AKbBUZKZeoWH0uzbU5w@public.gmane.org>
2004-01-20 21:17 ` Greg Sarjeant
[not found] ` <1074633425.3317.20.camel-bi+AKbBUZKZeoWH0uzbU5w@public.gmane.org>
2004-01-21 10:23 ` Ducrot Bruno
[not found] ` <20040121102356.GU25416-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org>
2004-01-21 15:25 ` Greg Sarjeant [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-01-21 0:23 Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A84702C9323C-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2004-01-24 19:58 ` Greg Sarjeant
2004-01-20 23:27 Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A8470255EFE4-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2004-01-21 0:07 ` Greg Sarjeant
2004-01-19 17:34 Greg Sarjeant
[not found] ` <1074533658.11008.18.camel-bi+AKbBUZKZeoWH0uzbU5w@public.gmane.org>
2004-01-19 19:51 ` Greg Sarjeant
[not found] ` <1074541900.2813.5.camel-bi+AKbBUZKZeoWH0uzbU5w@public.gmane.org>
2004-01-20 15:57 ` Greg Sarjeant
2004-01-20 20:03 ` Nate Lawson
[not found] ` <20040120120211.U96919-Y6VGUYTwhu0@public.gmane.org>
2004-01-21 10:11 ` Ducrot Bruno
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=1074698713.5964.23.camel@localhost \
--to=greg-qniyhhqvzb9kr2e5yswmoq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=ducrot-kk6yZipjEM5g9hUCZPvPmw@public.gmane.org \
--cc=nate-Y6VGUYTwhu0@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