.\" 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 "IDE_DO_DRIVE_CMD" "9" "09 October 2005" "" ""

.SH NAME
ide_do_drive_cmd \- issue IDE special command
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
int ide_do_drive_cmd  (ide_drive_t * \fIdrive\fB, struct request * \fIrq\fB, ide_action_t \fIaction\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIdrive\fB\fR
device to issue command
.TP
\fB\fIrq\fB\fR
request to issue
.TP
\fB\fIaction\fB\fR
action for processing
.SH "DESCRIPTION"
.PP
This function issues a special IDE device request
onto the request queue.
.PP
If action is ide_wait, then the rq is queued at the end of the
request queue, and the function sleeps until it has been processed.
This is for use when invoked from an ioctl handler.
.PP
If action is ide_preempt, then the rq is queued at the head of
the request queue, displacing the currently-being-processed
request and this function returns immediately without waiting
for the new rq to be completed.  This is VERY DANGEROUS, and is
intended for careful use by the ATAPI tape/cdrom driver code.
.PP
If action is ide_next, then the rq is queued immediately after
the currently-being-processed-request (if any), and the function
returns without waiting for the new rq to be completed.  As above,
This is VERY DANGEROUS, and is intended for careful use by the
ATAPI tape/cdrom driver code.
.PP
If action is ide_end, then the rq is queued at the end of the
request queue, and the function returns immediately without waiting
for the new rq to be completed. This is again intended for careful
use by the ATAPI tape/cdrom driver code.