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

.SH NAME
superhyway_add_device \- Add a SuperHyway module
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
int superhyway_add_device  (unsigned int \fImod_id\fB, unsigned long \fIbase\fB, unsigned long long \fIvcr\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fImod_id\fB\fR
Module ID (taken from MODULE.VCR.MOD_ID).
.TP
\fB\fIbase\fB\fR
Physical address where module is mapped.
.TP
\fB\fIvcr\fB\fR
VCR value.
.SH "DESCRIPTION"
.PP
This is responsible for adding a new SuperHyway module. This sets up a new
struct superhyway_device for the module being added. Each one of \fImod_id\fR,
\fIbase\fR, and \fIvcr\fR are registered with the new device for further use
elsewhere.
.PP
Devices are initially added in the order that they are scanned (from the
top-down of the memory map), and are assigned an ID based on the order that
they are added. Any manual addition of a module will thus get the ID after
the devices already discovered regardless of where it resides in memory.
.PP
Further work can and should be done in \fBsuperhyway_scan_bus\fR, to be sure
that any new modules are properly discovered and subsequently registered.