.\" This manpage has been automatically generated by docbook2man 
.\" from a DocBook document.  This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
.\" Please send any bug reports, improvements, comments, patches, 
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "DISK_SHOW" "9" "09 October 2005" "" ""

.SH NAME
disk_show \- Control suspend-to-disk mode
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
ssize_t disk_show  (struct subsystem * \fIsubsys\fB, char * \fIbuf\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIsubsys\fB\fR
-- undescribed --
.TP
\fB\fIbuf\fB\fR
-- undescribed --
.SH "DESCRIPTION"
.PP
.PP
Suspend-to-disk can be handled in several ways. The greatest
distinction is who writes memory to disk - the firmware or the OS.
If the firmware does it, we assume that it also handles suspending
the system.
If the OS does it, then we have three options for putting the system
to sleep - using the platform driver (e.g. ACPI or other PM registers),
powering off the system or rebooting the system (for testing).
.PP
The system will support either 'firmware' or 'platform', and that is
known a priori (and encoded in pm_ops). But, the user may choose
'shutdown' or 'reboot' as alternatives.
.PP
\fBshow\fR will display what the mode is currently set to.
\fBstore\fR will accept one of
.PP
'firmware'
'platform'
'shutdown'
'reboot'
.PP
It will only change to 'firmware' or 'platform' if the system
supports it (as determined from pm_ops->pm_disk_mode).