Date: Tue, 20 Jun 2000 08:55:31 +1000 From: "Andrew Reilly" <areilly@nsw.bigpond.net.au> 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 Subject: Re: ACPI project progress report Message-ID: <20000620085531.A38839@gurney.reilly.home> In-Reply-To: <45525.961432574@critter.freebsd.dk>; from phk@critter.freebsd.dk on Mon, Jun 19, 2000 at 06:36:14PM %2B0200 References: <200006191630.KAA60652@harmony.village.org> <45525.961432574@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
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 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000620085531.A38839>