From owner-acpi-jp@jp.freebsd.org  Tue Jun 20 00:32:30 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id AAA18596;
	Tue, 20 Jun 2000 00:32:30 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from tasogare.imasy.or.jp (daemon@tasogare.imasy.or.jp [202.227.24.5])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id AAA18588;
	Tue, 20 Jun 2000 00:32:28 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Received: from localhost (isdn38.imasy.or.jp [202.227.24.230])
	by tasogare.imasy.or.jp (8.10.1+3.3W/3.7W-tasogare/smtpfeed 1.07) with ESMTP id e5JFWMp82741;
	Tue, 20 Jun 2000 00:32:22 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
To: bfischer@Techfak.Uni-Bielefeld.DE
Cc: iwasaki@jp.freebsd.org, acpi-jp@jp.freebsd.org, dcs@newsguy.com,
        freebsd-current@FreeBSD.ORG, freebsd-hackers@FreeBSD.ORG
In-Reply-To: <20000619070144.B554@broccoli.no-support.loc>
References: <394AB05C.569DD4DD@newsguy.com>
	<20000617135611E.iwasaki@jp.FreeBSD.org>
	<20000619070144.B554@broccoli.no-support.loc>
X-Mailer: Mew version 1.94.1 on Emacs 19.34 / Mule 2.3 (SUETSUMUHANA)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <20000620003220R.iwasaki@jp.FreeBSD.org>
Date: Tue, 20 Jun 2000 00:32:20 +0900
From: Mitsuru IWASAKI <iwasaki@jp.freebsd.org>
X-Dispatcher: imput version 20000228(IM140)
Lines: 32
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 417
Subject: [acpi-jp 417] Re: ACPI project progress report
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: iwasaki@jp.freebsd.org

Hi,

From: Bjoern Fischer <bfischer@Techfak.Uni-Bielefeld.DE>
Subject: Re: ACPI project progress report
Date: Mon, 19 Jun 2000 07:01:44 +0200
Message-ID: <20000619070144.B554@broccoli.no-support.loc>

> Just a moment. You talk about doing a `Save-to-Disk' (incl. system halt),
> turning power off, maybe adding some hardware or moving the machine
> to another location, then switching on again, restoring the system context,
> and the machine will proceed as if nothing had happened, do you?

Yes, exactly.  My rough idea is like this;
 - do preparation for sleeping state transition for each devices and 
   _PTS (prepare to sleep) control method.
 - stop all of processes, other sub-system (eg filesystem, memory...)
   and write contents of memory to dedicated swap partition for
   "Save-to-Disk" and save system context.
 - turning power off by manipulating ACPI registers (or just halt the
   system and user will turning power off).
 - upon turning power on, BIOS built ACPI tables again if hardware
   configuration changed during sleeping. Any important device (eg
   disk controller) configuration changes will cause the restoring 
   system context to fail.
 - after POST, BIOS passes control to the boot loader in normal case.
 - load will check whether S4 transition occurred, then restore system
   context and memory from swap partition.
 - do _WAK (wakeup) control method, wakeup processes for each devices
   and re-enable them.

Maybe I'm wrong because of lack of my understanding on crush dump and
loader.  Please help us :-)
