[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87k5syg3yi.fsf@jbms.ath.cx>
Date: Tue, 17 Jul 2007 16:39:17 -0400
From: Jeremy Maitin-Shepard <jbms@....edu>
To: david@...g.hm
Cc: "Rafael J. Wysocki" <rjw@...k.pl>,
Alan Stern <stern@...land.harvard.edu>,
LKML <linux-kernel@...r.kernel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
"Huang\, Ying" <ying.huang@...el.com>,
Kyle Moffett <mrmacman_g4@....com>,
Nigel Cunningham <nigel@...el.suspend2.net>,
Pavel Machek <pavel@....cz>,
pm list <linux-pm@...ts.linux-foundation.org>,
Al Boldi <a1426z@...ab.com>
Subject: Re: Hibernation considerations
david@...g.hm writes:
[snip]
> the non-ACPI hibernate behaves very differently, and for some people (and I
> think I am one of them) it will meet their needs better then _any_ of the ACPI
> suspends.
It may have certain differences from the user point of view, but from
the implementation view, it seems that it is nearly exactly the same.
The only differences seem to be:
- rather than shutting down, do whatever is necessary to stick the
system in S4 state.
- make sure ACPI isn't initialized by the "load image" kernel
- rather than "resume from hibernate" ACPI by initializing it normally,
issue the special hibernate-related methods.
Thus, it seems that supporting ACPI S4 will have a very minimal affect
on the hibernate implementation.
--
Jeremy Maitin-Shepard
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists