1<html><head><meta http-equiv="Content-Type" content="text/html; charset=ANSI_X3.4-1968"><title>z8530_rx</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"><link rel="home" href="index.html" title="Z8530 Programming Guide"><link rel="up" href="intfunctions.html" title="Chapter&#160;10.&#160;Internal Functions"><link rel="prev" href="API-z8530-rtsdtr.html" title="z8530_rtsdtr"><link rel="next" href="API-z8530-tx.html" title="z8530_tx"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center"><span class="phrase">z8530_rx</span></th></tr><tr><td width="20%" align="left"><a accesskey="p" href="API-z8530-rtsdtr.html">Prev</a>&#160;</td><th width="60%" align="center">Chapter&#160;10.&#160;Internal Functions</th><td width="20%" align="right">&#160;<a accesskey="n" href="API-z8530-tx.html">Next</a></td></tr></table><hr></div><div class="refentry"><a name="API-z8530-rx"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>z8530_rx &#8212; 
2     Handle a PIO receive event
3 </p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="funcsynopsis"><table border="0" class="funcprototype-table" summary="Function synopsis" style="cellspacing: 0; cellpadding: 0;"><tr><td><code class="funcdef">void <b class="fsfunc">z8530_rx </b>(</code></td><td>struct z8530_channel * <var class="pdparam">c</var><code>)</code>;</td></tr></table><div class="funcprototype-spacer">&#160;</div></div></div><div class="refsect1"><a name="idp1119448468"></a><h2>Arguments</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term"><em class="parameter"><code>c</code></em></span></dt><dd><p>
4     Z8530 channel to process
5    </p></dd></dl></div></div><div class="refsect1"><a name="idp1119450036"></a><h2>Description</h2><p>
6   Receive handler for receiving in PIO mode. This is much like the 
7   async one but not quite the same or as complex
8</p></div><div class="refsect1"><a name="idp1119450740"></a><h2>Note</h2><p>
9   Its intended that this handler can easily be separated from
10   the main code to run realtime. That'll be needed for some machines
11   (eg to ever clock 64kbits on a sparc ;)).
12   </p><p>
13
14   The RT_LOCK macros don't do anything now. Keep the code covered
15   by them as short as possible in all circumstances - clocks cost
16   baud. The interrupt handler is assumed to be atomic w.r.t. to
17   other code - this is true in the RT case too.
18   </p><p>
19
20   We only cover the sync cases for this. If you want 2Mbit async
21   do it yourself but consider medical assistance first. This non DMA 
22   synchronous mode is portable code. The DMA mode assumes PCI like 
23   ISA DMA
24   </p><p>
25
26   Called with the device lock held
27</p></div></div><div class="navfooter"><hr><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="API-z8530-rtsdtr.html">Prev</a>&#160;</td><td width="20%" align="center"><a accesskey="u" href="intfunctions.html">Up</a></td><td width="40%" align="right">&#160;<a accesskey="n" href="API-z8530-tx.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top"><span class="phrase">z8530_rtsdtr</span>&#160;</td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top">&#160;<span class="phrase">z8530_tx</span></td></tr></table></div></body></html>
28