public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Sarjeant <greg-QNIYhHqVzB9kr2E5YSwMOQ@public.gmane.org>
To: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Gateway 200X (again) - No power button events
Date: Mon, 19 Jan 2004 14:51:41 -0500	[thread overview]
Message-ID: <1074541900.2813.5.camel@localhost> (raw)
In-Reply-To: <1074533658.11008.18.camel-bi+AKbBUZKZeoWH0uzbU5w@public.gmane.org>

OK, I found the Notify call that I was looking for. It was in the
EmbeddedControl region, and they don't specify the \_SB. prefix:

   Method (_Q50, 0, NotSerialized)
   {
       Notify (PWRB, 0x80)
   }

So, it looks like it is specified in the DSDT. I'm not sure why I don't
get an event when I press the button. I do get events from the sleep
button, but the two are declared somewhat differently. Here they are for
comparison:

        Device (SLPB)
        {
            Name (_HID, EisaId ("PNP0C0E"))
            Method (_STA, 0, NotSerialized)
            {
                Return (0x0F)
            }
        }

        Device (PWRB)
        {
            Name (_HID, EisaId ("PNP0C0C"))
            Name (_PRW, Package (0x02)
            {
                0x1D, 
                0x04
            })
        }


Thanks again,
  Greg


On Mon, 2004-01-19 at 12:34, Greg Sarjeant wrote:
> Hi,
> 
>     I have another question about my Gateway 200X. ACPI is working much
> better now, but I just started playing with the power button, and it
> turns out that I am not getting any events from it. I looked through the
> DSDT, and could not find any Notify (\SW.PWRB, 0x80) statements for it,
> so I imagine that that is the problem. Here (I think) are the relevant
> DSDT sections:
> 
> 
>     Scope (_GPE)
>     {
>         Method (_L05, 0, NotSerialized)
>         {
>             Notify (\_SB.PCI0.MODM, 0x02)
>             Notify (\_SB.PWRB, 0x02)
>         }
> 
>         Method (_L0B, 0, NotSerialized)
>         {
>             Notify (\_SB.PCI0.PCIB, 0x02)
>             Notify (\_SB.PWRB, 0x02)
>         }
> 
>         Method (_L1D, 0, NotSerialized)
>         {
>             Store (\_SB.PHS1 (0x8E, Zero), Local0)
>             If (LEqual (Local0, One))
>             {
>                 Notify (\_SB.PWRB, 0x02)
>             }
> 
>             If (LEqual (Local0, 0x02))
>             {
>                 Notify (\_SB.PWRB, 0x02)
>             }
>         }
>     }
> 
> 
>     Device (PWRB)
>     {
>         Name (_HID, EisaId ("PNP0C0C"))
>         Name (_PRW, Package (0x02)
>         {
>             0x1D, 
>             0x04
>         })
>     }
> 
> 
> Do I have to add this Notify statement in the _GPE block? I'm also a bit
> confused by the "Notify (\_SB.PWRB, 0x02)" lines. From the spec, I
> thought that 0x80 and 0x200 were the expected values from Notify for the
> power button. Am I missing something here?
> 
> Also, the BIOS does not supply an ECDT. I am using the patch at bug 1690
> to get around this, could that be related? 
> 
> The power button does shut the macine down in Windows XP. I have tried
> passing acpi_os_name="Microsoft Windows XP" to the kernel without
> success. I did that because I noticed lines like this:
> 
>        If (LEqual (SizeOf (_OS), 0x14))
> 
> In the PCI0 device block after seeing the S3D method emails. I haven't
> really had the chance to dig into what's going on there yet, so it was a
> bit of a blind stab.
> 
> For reference, the complete DSDT is posted at
> http://www.morningdave.org/acpi/dsdt.dsl
> 
> 
> Thanks again for any help,
> 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
> _______________________________________________
> Acpi-devel mailing list
> Acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
> https://lists.sourceforge.net/lists/listinfo/acpi-devel
> 



-------------------------------------------------------
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-01-19 19:51 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-19 17:34 Gateway 200X (again) - No power button events Greg Sarjeant
     [not found] ` <1074533658.11008.18.camel-bi+AKbBUZKZeoWH0uzbU5w@public.gmane.org>
2004-01-19 19:51   ` Greg Sarjeant [this message]
     [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
  -- strict thread matches above, loose matches on Subject: below --
2004-01-20 20:15 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
2004-01-20 23:27 Grover, Andrew
     [not found] ` <F760B14C9561B941B89469F59BA3A8470255EFE4-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2004-01-21  0:07   ` Greg Sarjeant
2004-01-21  0:23 Grover, Andrew
     [not found] ` <F760B14C9561B941B89469F59BA3A84702C9323C-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2004-01-24 19:58   ` Greg Sarjeant

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=1074541900.2813.5.camel@localhost \
    --to=greg-qniyhhqvzb9kr2e5yswmoq@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