From: Pavel Machek <pavel-+ZI9xUNit7I@public.gmane.org>
To: Stefan Seyfried
<seife-T+3qhDtrTvDv8lqoKu5MV4HBZQ1bDw0s@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: Re: acpi: sleep/proc.c cleanups
Date: Thu, 31 Mar 2005 16:27:25 +0200 [thread overview]
Message-ID: <20050331142724.GA609@openzaurus.ucw.cz> (raw)
In-Reply-To: <20050319223115.GC29495-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>
Hi!
> > --- clean/drivers/acpi/sleep/proc.c 2005-01-12 11:07:39.000000000 +0100
> > +++ linux/drivers/acpi/sleep/proc.c 2005-01-12 11:20:13.000000000 +0100
>
> > + seq_printf(seq, "%4s %4d %s%8s\n",
> > + dev->pnp.bus_id, (u32) dev->wakeup.sleep_state,
> > + dev->wakeup.flags.run_wake ? "*" : "",
> > + dev->wakeup.state.enabled ? "enabled" : "disabled");
>
> Oh, now that i read this... :-)
>
> What is the difference beteen "*enabled" and "enabled"? I noticed it today
> when trying to get my Armada E500 to wake-on-lan from S3. So what is
> wakeup.flags.run_wake?
Not quite sure, probably something to do with runtime wakeups :-).
Pavel
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
-------------------------------------------------------
This SF.net email is sponsored by Demarc:
A global provider of Threat Management Solutions.
Download our HomeAdmin security software for free today!
http://www.demarc.com/Info/Sentarus/hamr30
prev parent reply other threads:[~2005-03-31 14:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-19 11:06 acpi: sleep/proc.c cleanups Pavel Machek
[not found] ` <20050319110657.GA1530-I/5MKhXcvmPrBKCeMvbIDA@public.gmane.org>
2005-03-19 22:31 ` Stefan Seyfried
[not found] ` <20050319223115.GC29495-l0tNAEGuAhhzZ8+rp42Dbp9+tswZ0GTaehPwdyo5hKaELgA04lAiVw@public.gmane.org>
2005-03-31 14:27 ` Pavel Machek [this message]
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=20050331142724.GA609@openzaurus.ucw.cz \
--to=pavel-+zi9xunit7i@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=seife-T+3qhDtrTvDv8lqoKu5MV4HBZQ1bDw0s@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