From: Nate Lawson <nate-Y6VGUYTwhu0@public.gmane.org>
To: Dominik Brodowski
<linux-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
Cc: acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: S3-resume in FreeBSD
Date: Fri, 9 Apr 2004 15:58:23 -0700 (PDT) [thread overview]
Message-ID: <20040409154821.R50561@root.org> (raw)
In-Reply-To: <20040409061527.GA8572-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
On Fri, 9 Apr 2004, Dominik Brodowski wrote:
> Do you know, by chance, if FreeBSD's resume process from S3 equals
> acpi_sleep=s3_mode, s3_bios or none of these special hacks?
>
> Many thanks,
> Dominik
I don't actually know what those flags do on Linux. You can see the path
taken for suspend/resume by following these functions in the linked files:
http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/dev/acpica/acpi.c?rev=1.136&content-type=text/plain
acpi_SetSleepState()
http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/i386/acpica/acpi_wakeup.c?rev=1.31&content-type=text/plain
acpi_sleep_machdep()
[sleep S3, wakeup]
http://www.freebsd.org/cgi/cvsweb.cgi/~checkout~/src/sys/i386/acpica/acpi_wakecode.S?rev=1.9
acpi wakecode runs and returns to acpi_restorecpu() (in acpi_wakeup.c)
We just committed code to save/restore BARs for PCI devices. That should
fix some problems. We support _PRW/_PSW so lid switch wakes devices.
Things left to do include _SxD support and I think there are some problems
with the ACPI-CA path for suspend/resume (i.e. it doesn't always clear
wake status).
-Nate
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
prev parent reply other threads:[~2004-04-09 22:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-08 20:38 Fix wake GPE enabling Moore, Robert
[not found] ` <37F890616C995246BE76B3E6B2DBE0554F1C5F-sBd4vmA9Se5Qxe9IK+vIArfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2004-04-08 22:20 ` Nate Lawson
[not found] ` <20040409061527.GA8572@dominikbrodowski.de>
[not found] ` <20040409061527.GA8572-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@public.gmane.org>
2004-04-09 22:58 ` Nate Lawson [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=20040409154821.R50561@root.org \
--to=nate-y6vguytwhu0@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=linux-X3ehHDuj6sIIGcDfoQAp7BvVK+yQ3ZXh@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