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

.SH NAME
hub_set_piomode \- set pio mode for a given hub
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
void hub_set_piomode  (nasid_t \fInasid\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fInasid\fB\fR
physical node ID for the hub in question
.SH "DESCRIPTION"
.PP
Put the hub into either ``PIO conveyor belt'' mode or ``fire-and-forget'' mode.
To do this, we have to make absolutely sure that no PIOs are in progress
so we turn off access to all widgets for the duration of the function.
.PP
XXX - This code should really check what kind of widget we're talking
to.  Bridges can only handle three requests, but XG will do more.
How many can crossbow handle to widget 0?  We're assuming 1.
.PP
XXX - There is a bug in the crossbow that link reset PIOs do not
return write responses.  The easiest solution to this problem is to
leave widget 0 (xbow) in fire-and-forget mode at all times.  This
only affects pio's to xbow registers, which should be rare.
.SH "DESCRIPTION"
.PP
Put the hub into either ``PIO conveyor belt'' mode or ``fire-and-forget'' mode.
To do this, we have to make absolutely sure that no PIOs are in progress
so we turn off access to all widgets for the duration of the function.
.PP
XXX - This code should really check what kind of widget we're talking
to.  Bridges can only handle three requests, but XG will do more.
How many can crossbow handle to widget 0?  We're assuming 1.
.PP
XXX - There is a bug in the crossbow that link reset PIOs do not
return write responses.  The easiest solution to this problem is to
leave widget 0 (xbow) in fire-and-forget mode at all times.  This
only affects pio's to xbow registers, which should be rare.