public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell Neches <russell-1vnkWVZi4QaVc3sceRu5cw@public.gmane.org>
To: Vernon Mauery <vernux-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: acpi-devel
	<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: bug in acpid scripts
Date: Fri, 23 Jul 2004 19:34:12 -0400	[thread overview]
Message-ID: <20040723233412.GA9078@omocha.vort.org> (raw)
In-Reply-To: <1090615197.9015.7.camel-DNmeG3802II@public.gmane.org>

> Adding new wakeup devices helps in this area a lot.  Check out the
> latest acpi patch to the kernel -- I had this same issue and applied
> the  acpi-20040715 patch, which among other things adds support for
> other things waking up the machine (sleep button, lid, etc.)
> 
> This simply makes it so you don't have to press the power button to
> wake up from S3.  While that is not exactly a direct solution, it was
> the one I was looking for anyway.

Interesting, though I think the only thing my laptop would be able to
use to trigger S3 would be the lid switch, and I don't think I'd want
that. I think one of the best things about Apple's laptops is how
awesome their sleep support is. The worst thing about them (in my
opinion) that they make it a nightmare to disable the sleep-on-lid-close
feature.

Obviously, some people will love it, so I'm very pleased that we can
configure S3/wakup triggers that way. But, considering tha S3 still
breaks things... 

Oi.

Russell


-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click

  parent reply	other threads:[~2004-07-23 23:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-23 19:36 bug in acpid scripts Russell Neches
     [not found] ` <20040723193658.GA3331-5z3TbH0F9hyr8sbHwu5NIg@public.gmane.org>
2004-07-23 20:39   ` Vernon Mauery
     [not found]     ` <1090615197.9015.7.camel-DNmeG3802II@public.gmane.org>
2004-07-23 23:34       ` Russell Neches [this message]
2004-07-24 12:50   ` Matthew Garrett
     [not found]     ` <1090673420.4412.14.camel-myFlNLNQP+Q@public.gmane.org>
2004-07-24 13:51       ` Mattia Dongili
     [not found]         ` <20040724135111.GC2328-MEqNC12sBsHxa7XIdbXXog@public.gmane.org>
2004-07-24 14:40           ` Luca Capello
2004-08-11 13:40   ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2004-07-24 13:23 Li, Shaohua
     [not found] ` <B44D37711ED29844BEA67908EAF36F03665E4F-4yWAQGcml65pB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-07-25  1:42   ` Russell Neches
2004-08-12  7:07 Li, Shaohua
     [not found] ` <B44D37711ED29844BEA67908EAF36F038AD732-4yWAQGcml65pB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-08-13  0:24   ` Nathan Bryant
2004-08-13  6:18   ` Stefan Seyfried
2004-08-13  0:52 Li, Shaohua
     [not found] ` <B44D37711ED29844BEA67908EAF36F038ADB3E-4yWAQGcml65pB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-08-13  0:55   ` Nathan Bryant

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=20040723233412.GA9078@omocha.vort.org \
    --to=russell-1vnkwvzi4qavc3sceru5cw@public.gmane.org \
    --cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    --cc=vernux-r/Jw6+rmf7HQT0dZR+AlfA@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