From: Nigel Cunningham <ncunningham-oKK1aGe2n869koe0gwxAeg@public.gmane.org>
To: "Grover, Andrew" <andrew.grover-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: ACPI List <acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: Documentation was: Power on at specified time.
Date: Wed, 19 Feb 2003 19:25:28 +1300 [thread overview]
Message-ID: <1045635927.4398.7.camel@laptop-linux.cunninghams> (raw)
In-Reply-To: <F760B14C9561B941B89469F59BA3A84725A18F-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
> Speaking of that, there currently isn't a Documentation/acpi directory,
> although I know a number of people have written some good write-ups of
> various things - maybe that's where they should go.
Well, I found a nvram-wakeup project on Sourceforge. I managed to
download it from elsewhere (since Sorceforge is currently down), and it
looks from that like every manufacturer has a different method of
implementing this. I looked through the ACPI specs I have downloaded,
but didn't see anything that indicated a standardised way of telling the
computer to wake up at a specific time. Patrick's code uses the RTC
alarm but from that nvram-wakeup project, this is by no means the only
method. What is more, the project says that sometime the wakeup time
doesn't 'take' until after a reboot!
Regards,
Nigel
-------------------------------------------------------
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most comprehensive and flexible code editor you can use.
Code faster. C/C++, C#, Java, HTML, XML, many more. FREE 30-Day Trial.
www.slickedit.com/sourceforge
prev parent reply other threads:[~2003-02-19 6:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-19 1:01 Documentation was: Power on at specified time Grover, Andrew
[not found] ` <F760B14C9561B941B89469F59BA3A84725A18F-sBd4vmA9Se4Lll3ZsUKC9FDQ4js95KgL@public.gmane.org>
2003-02-19 6:25 ` Nigel Cunningham [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=1045635927.4398.7.camel@laptop-linux.cunninghams \
--to=ncunningham-okk1age2n869koe0gwxaeg@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=andrew.grover-ral2JQCrhuEAvxtiuMwx3w@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