public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: "Scott T. Smith" <scott-j3vAvQ9dNB9ByuSxxbvQtw@public.gmane.org>
To: Greg Sarjeant <greg-QNIYhHqVzB9kr2E5YSwMOQ@public.gmane.org>
Cc: "acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org"
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: broken power button
Date: Thu, 05 Feb 2004 21:07:26 -0800	[thread overview]
Message-ID: <1076044045.4744.10.camel@tinny.home.foo> (raw)
In-Reply-To: <1076038435.5849.8.camel-bi+AKbBUZKZeoWH0uzbU5w@public.gmane.org>

On Thu, 2004-02-05 at 19:33, Greg Sarjeant wrote:
>     I have the same issue with my power button on my Gateway 200X (which
> I think is roughly the same machine as the Dell X200). It appears to be

the older ones are identical AFAIK; the newer 200X's have 14" screens
though and seem totally different.

> an issue with fixed-feature power buttons. I opened bug 1920 to address
> the problem. You can check it out here:

I applied the patch; I think ACPI should report a warning in this case. 
According to p63, there are 2 bits of information (4 choices) but only 2
legal possibilities.  Windows must be ignoring the PWR_BUTTON field and
just checking for the existance of PWRB.  ACPI should complain if
PWR_BUTTON is not set and PWRB exists, or if PWR_BUTTON is set and PWRB
doesn't exist.

Similarly, if SLP_BUTTON is not set and SLPB exists, ACPI should throw a
warning too.

Unfortunately, while this lets me receive PWRB notifications, it doesn't
solve the lockup on suspend.  Ugh.

	Scott



-------------------------------------------------------
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

  parent reply	other threads:[~2004-02-06  5:07 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-06  2:55 broken power button Scott T. Smith
     [not found] ` <1076036158.4792.12.camel-3lu5YwujmwObGSPjaX/RoA@public.gmane.org>
2004-02-06  3:33   ` Greg Sarjeant
     [not found]     ` <1076038435.5849.8.camel-bi+AKbBUZKZeoWH0uzbU5w@public.gmane.org>
2004-02-06  5:07       ` Scott T. Smith [this message]
     [not found]         ` <1076044045.4744.10.camel-3lu5YwujmwObGSPjaX/RoA@public.gmane.org>
2004-02-06 12:46           ` Greg Sarjeant
  -- strict thread matches above, loose matches on Subject: below --
2004-02-06 17:17 Yu, Luming
     [not found] ` <3ACA40606221794F80A5670F0AF15F8401CBB686-SRlDPOYGfgogGBtAFL8yw7fspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-02-06 17:38   ` Scott T. Smith
     [not found]     ` <1076089128.4731.1.camel-3lu5YwujmwObGSPjaX/RoA@public.gmane.org>
2004-02-06 17:53       ` greg
2004-02-06 17:53   ` Scott T. Smith
2004-02-11  8:02 Yu, Luming

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=1076044045.4744.10.camel@tinny.home.foo \
    --to=scott-j3vavq9dnb9byusxxbvqtw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=greg-QNIYhHqVzB9kr2E5YSwMOQ@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