.\" 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 "MCA_WRITE_POS" "" "06 October 2005" "" ""

.SH NAME
mca_write_pos \- read POS register from card
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
void mca_write_pos  (int \fIslot\fB, int \fIreg\fB, unsigned char \fIbyte\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIslot\fB\fR
slot number to read from
.TP
\fB\fIreg\fB\fR
register to read from
.TP
\fB\fIbyte\fB\fR
byte to write to the POS registers
.SH "DESCRIPTION"
.PP
Store a POS value directly from the hardware. You should not
normally need to use this function and should have a very good
knowledge of MCA bus before you do so. Doing this wrongly can
damage the hardware.
.PP
This function may not be used from interrupt context.
.PP
Note that this a technically a Bad Thing, as IBM tech stuff says
you should only set POS values through their utilities.
However, some devices such as the 3c523 recommend that you write
back some data to make sure the configuration is consistent.
I'd say that IBM is right, but I like my drivers to work.
.PP
This function can't do checks to see if multiple devices end up
with the same resources, so you might see magic smoke if someone
screws up.