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

.SH NAME
z8530_rx \- Handle a PIO receive event
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
void z8530_rx  (struct z8530_channel * \fIc\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIc\fB\fR
Z8530 channel to process
.SH "DESCRIPTION"
.PP
Receive handler for receiving in PIO mode. This is much like the 
async one but not quite the same or as complex
.SH "NOTE"
.PP
Its intended that this handler can easily be separated from
the main code to run realtime. That'll be needed for some machines
(eg to ever clock 64kbits on a sparc ;)).
.PP
The RT_LOCK macros don't do anything now. Keep the code covered
by them as short as possible in all circumstances - clocks cost
baud. The interrupt handler is assumed to be atomic w.r.t. to
other code - this is true in the RT case too.
.PP
We only cover the sync cases for this. If you want 2Mbit async
do it yourself but consider medical assistance first. This non DMA 
synchronous mode is portable code. The DMA mode assumes PCI like 
ISA DMA
.PP
Called with the device lock held