From owner-acpi-jp@jp.freebsd.org  Tue Jun 20 07:56:12 2000
Received: (from daemon@localhost)
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) id HAA42006;
	Tue, 20 Jun 2000 07:56:12 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from sr14.nsw-remote.bigpond.net.au ([24.192.3.29])
	by castle.jp.freebsd.org (8.9.3+3.2W/8.7.3) with ESMTP id HAA42000
	for <acpi-jp@jp.freebsd.org>; Tue, 20 Jun 2000 07:56:09 +0900 (JST)
	(envelope-from areilly@nsw.bigpond.net.au)
Received: from areilly.bpc-users.org (CPE-144-132-171-71.nsw.bigpond.net.au [144.132.171.71])
	by sr14.nsw-remote.bigpond.net.au (Pro-8.9.3/8.9.3) with SMTP id IAA16331
	for <acpi-jp@jp.freebsd.org>; Tue, 20 Jun 2000 08:55:34 +1000 (EST)
Received: (qmail 38927 invoked by uid 1000); 19 Jun 2000 22:55:31 -0000
From: "Andrew Reilly" <areilly@nsw.bigpond.net.au>
Date: Tue, 20 Jun 2000 08:55:31 +1000
To: Poul-Henning Kamp <phk@critter.freebsd.dk>
Cc: Warner Losh <imp@village.org>, 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
Message-ID: <20000620085531.A38839@gurney.reilly.home>
References: <200006191630.KAA60652@harmony.village.org> <45525.961432574@critter.freebsd.dk>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.2i
In-Reply-To: <45525.961432574@critter.freebsd.dk>; from phk@critter.freebsd.dk on Mon, Jun 19, 2000 at 06:36:14PM +0200
Reply-To: acpi-jp@jp.freebsd.org
Precedence: list
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+000315
X-Sequence: acpi-jp 422
Subject: [acpi-jp 422] Re: ACPI project progress report
Errors-To: owner-acpi-jp@jp.freebsd.org
Sender: owner-acpi-jp@jp.freebsd.org
X-Originator: areilly@nsw.bigpond.net.au

On Mon, Jun 19, 2000 at 06:36:14PM +0200, Poul-Henning Kamp wrote:
> 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.

That sounds way too hard.  Why not restrict suspend activity to
user-level processes and bring the kernel/drivers back up through
a regular boot process?  At least that way the hardware and drivers
will know what they are all up to, even if some of it has changed
in the mean time.

> 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"

Yeah.  The X server has far too much "driver" level code in it
already, so probably needs to be tweaked to re-initialise itself
properly.

-- 
Andrew
