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

.SH NAME
drm_infobufs \- 
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
int drm_infobufs  (struct inode * \fIinode\fB, struct file * \fIfilp\fB, unsigned int \fIcmd\fB, unsigned long \fIarg\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIinode\fB\fR
-- undescribed --
.TP
\fB\fIfilp\fB\fR
-- undescribed --
.TP
\fB\fIcmd\fB\fR
-- undescribed --
.TP
\fB\fIarg\fB\fR
-- undescribed --
.SH "DESCRIPTION"
.PP
.PP
This was originally mean for debugging purposes, or by a sophisticated
client library to determine how best to use the available buffers (e.g.,
large buffers can be used for image transfer).
.PP
\\param inode device inode.
\\param filp file pointer.
\\param cmd command.
\\param arg pointer to a drm_buf_info structure.
\\return zero on success or a negative number on failure.
.SH "INCREMENTS DRM_DEVICE"
.PP
:buf_use while holding the drm_device::count_lock
lock, preventing of allocating more buffers after this call. Information
about each requested buffer is then copied into user space.