From owner-acpi-jp@jp.freebsd.org  Tue Jun 20 01:36:37 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id BAA22648;
	Tue, 20 Jun 2000 01:36:37 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id BAA22642;
	Tue, 20 Jun 2000 01:36:33 +0900 (JST)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.9.3/8.9.3) with ESMTP id SAA45527;
	Mon, 19 Jun 2000 18:36:14 +0200 (CEST)
	(envelope-from phk@critter.freebsd.dk)
To: Warner Losh <imp@village.org>
cc: Mitsuru IWASAKI <iwasaki@jp.freebsd.org>,
        bfischer@Techfak.Uni-Bielefeld.DE, acpi-jp@jp.freebsd.org,
        dcs@newsguy.com, freebsd-current@FreeBSD.ORG,
        freebsd-hackers@FreeBSD.ORG
In-reply-to: Your message of "Mon, 19 Jun 2000 10:30:53 MDT."
             <200006191630.KAA60652@harmony.village.org> 
Date: Mon, 19 Jun 2000 18:36:14 +0200
Message-ID: <45525.961432574@critter.freebsd.dk>
From: Poul-Henning Kamp <phk@critter.freebsd.dk>
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 420
Subject: [acpi-jp 420] Re: ACPI project progress report 
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: phk@critter.freebsd.dk

In message <200006191630.KAA60652@harmony.village.org>, Warner Losh writes:
>In message <20000620003220R.iwasaki@jp.FreeBSD.org> Mitsuru IWASAKI writes:
>: Maybe I'm wrong because of lack of my understanding on crush dump and
>: loader.  Please help us :-)
>
>I think that you might be able to do this.  The real tricky part maybe
>saving hardware RAM that the drivers expect to be there when you
>wakeup.  I thinking of video ram and the X server's font cache, to
>name one example.

Drivers will need a "your hardware may have been zonked" entrypoint,
think about the i8254 counter or all the weird versions of write
only or "write here - read there" I/O registers in existence.

Obviously the video driver will need to send a signal or clue to the
Xserver saying "you own the device, you'd better do something"

--
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD coreteam member | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.
