What does X need PM for anyway?

[Jay Cotton]

The short answer is eStar..   Government buyers require eStart compliance.

The X server needs to be involved with power management for a number of 
reasons, however on some
systems its possible to power down parts of the machine (graphics for 
instance) and leave the rest up.
So, in this case the x server is still trying to write on the display, 
but, with the power off, its likely to
segfault unless the server and ddx know what state the buss and display 
h/w is in.

The signals are generated by the kernel and passed to the server via 
APM, and I suppose ACPI at some
time in the future.  The server then processes the 'signals' and sets up 
the h/w for the various power
states.

I have done implementations of DPMS, Suspend/Resume, and FBPM (a new 
possible standard) that Sun
uses on Sparc.



kim at klassmaster.com wrote:

>Hi,
>
>there has been this checkin to CVS which has kind of puzzled me:
>
><URI:http://cvs.freedesktop.org/xorg/xc/ChangeLog?rev=1.1226&view=markup>
>
>The question I'm wondering about is, what is any X driver supposed to do
>with these events? I hear that this only includes power management
>related events. Does X need to save state, does it restart parts of
>itself, or does it need to block a suspend process if it can't cope with
>it?
>
>Furthermore, which drivers actually handle ACPI events? I haven't been
>unable to get a definite answer on #xorg, that's why I'm asking here.
>
>TIA,
>Kim Krecht
>_______________________________________________
>xorg mailing list
>xorg at lists.freedesktop.org
>http://lists.freedesktop.org/mailman/listinfo/xorg
>  
>