Hi!
> > Oh hey, look at "check_events". You are right.
> > It doesn't look like notifiers will be called on
> > critical suspend (no call to send_event or
> > directly to pm_send_all).
> >
> > Stephen, this is a bug, right? Or intended?
>
> No, it is not a bug. To quote the APM spec:
APM spec is useless, here. We are talking kernel drivers, not
applications. We have full control on kernel drivers, and if some
takes too much time to process, we may just fix it. I suggest just
sending normal suspend request to whole kernel -- 5 seconds is a lot
of time. [I need it for usb, I guess.]
> "However, once the APM Driver receives the Critical Suspend Notification,
> the BIOS must wait at least 5 seconds from the time that the APM Driver
> recieves the Critical Suspend Notification for it to call the Set Power
> State to suspend (BX=0001H, CX=0002H). This must be done because it
> may not be possible to properly resume the devices in the system if it
> is suspended before the operating system becomes aware of the impending
> shutdown."
Right. I can not easily resume USB if it was not properly
suspended. And notifying everyone in-kernel seems like good idea,
anyway.
> So, I am open to suggestions ...
Just send normal suspend request inside kernel.
--
The best software in life is free (not shareware)! Pavel
GCM d? s-: !g p?:+ au- a--@ w+ v- C++@ UL+++ L++ N++ E++ W--- M- Y- R+
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]