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

.SH NAME
transport_setup_device \- declare a new dev for transport class association
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
void transport_setup_device  (struct device * \fIdev\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIdev\fB\fR
the generic device representing the entity being added
.SH "DESCRIPTION"
.PP
Usually, dev represents some component in the HBA system (either
the HBA itself or a device remote across the HBA bus).  This
routine is simply a trigger point to see if any set of transport
classes wishes to associate with the added device.  This allocates
storage for the class device and initialises it, but does not yet
add it to the system or add attributes to it (you do this with
transport_add_device).  If you have no need for a separate setup
and add operations, use transport_register_device (see
transport_class.h).
.SH "DESCRIPTION"
.PP
Usually, dev represents some component in the HBA system (either
the HBA itself or a device remote across the HBA bus).  This
routine is simply a trigger point to see if any set of transport
classes wishes to associate with the added device.  This allocates
storage for the class device and initialises it, but does not yet
add it to the system or add attributes to it (you do this with
transport_add_device).  If you have no need for a separate setup
and add operations, use transport_register_device (see
transport_class.h).