On Mon, Jun 19, 2000 at 06:36:14PM +0200, Poul-Henning Kamp wrote:
> In message <[EMAIL PROTECTED]>, Warner Losh writes:
> >In message <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-hackers" in the body of the message
