From owner-freebsd-current Wed Jun 21 3:47:59 2000 Delivered-To: freebsd-current@freebsd.org Received: from haldjas.folklore.ee (Haldjas.folklore.ee [193.40.6.121]) by hub.freebsd.org (Postfix) with ESMTP id 40C5F37BB81 for ; Wed, 21 Jun 2000 03:47:53 -0700 (PDT) (envelope-from narvi@haldjas.folklore.ee) Received: from localhost (narvi@localhost) by haldjas.folklore.ee (8.9.3/8.9.3) with SMTP id MAA91783; Wed, 21 Jun 2000 12:45:24 +0200 (EET) (envelope-from narvi@haldjas.folklore.ee) Date: Wed, 21 Jun 2000 12:45:24 +0200 (EET) From: Narvi To: Warner Losh Cc: freebsd-current@FreeBSD.ORG Subject: Re: ACPI project progress report In-Reply-To: <200006202247.QAA75403@harmony.village.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue, 20 Jun 2000, Warner Losh wrote: > In message Narvi writes: > : You obviously haven't considered the ability to be able to near hot-swap > : motherboard and cpu - or even RAM - in this way. > > The ACPI spec specifically states that one cannot disassemble a > machine in S4 state and expect the state to be saved on reassembly. > Maybe the same sort of mechanism could be used to do this, but then > again, maybe night. > At any rate, being able to save and then restore the state would be the needed inital step in reassembly related state saves/recoveres. > Warner > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message