diff options
Diffstat (limited to 'static/netbsd/man4/man4.vax/ec.4 4.html')
| -rw-r--r-- | static/netbsd/man4/man4.vax/ec.4 4.html | 91 |
1 files changed, 0 insertions, 91 deletions
diff --git a/static/netbsd/man4/man4.vax/ec.4 4.html b/static/netbsd/man4/man4.vax/ec.4 4.html deleted file mode 100644 index b004089a..00000000 --- a/static/netbsd/man4/man4.vax/ec.4 4.html +++ /dev/null @@ -1,91 +0,0 @@ -<table class="head"> - <tr> - <td class="head-ltitle">EC(4)</td> - <td class="head-vol">Device Drivers Manual (vax)</td> - <td class="head-rtitle">EC(4)</td> - </tr> -</table> -<div class="manual-text"> -<section class="Sh"> -<h1 class="Sh" id="NAME"><a class="permalink" href="#NAME">NAME</a></h1> -<p class="Pp"><code class="Nm">ec</code> — <span class="Nd">3Com 10 Mb/s - Ethernet interface</span></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="SYNOPSIS"><a class="permalink" href="#SYNOPSIS">SYNOPSIS</a></h1> -<p class="Pp"><code class="Cd">ec0 at uba0 csr 161000 vector ecrint eccollide - ecxint flags 0</code></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1> -<p class="Pp">NOTE: This driver has not been ported from - <span class="Ux">4.4BSD</span> yet.</p> -<p class="Pp">The <code class="Nm">ec</code> interface provides access to a 10 - Mb/s Ethernet network through a 3Com controller.</p> -<p class="Pp">The hardware has 32 kilobytes of dual-ported memory on the UNIBUS. - This memory is used for internal buffering by the board, and the interface - code reads the buffer contents directly through the UNIBUS. The address of - this memory is given in the <var class="Ar">flags</var> field in the - configuration file. The first interface normally has its memory at UNIBUS - address 0.</p> -<p class="Pp">Each of the host's network addresses is specified at boot time - with an <code class="Dv">SIOCSIFADDR</code> <a class="Xr">ioctl(2)</a>. The - <code class="Nm">ec</code> interface employs the address resolution protocol - described in <a class="Xr">arp(4)</a> to dynamically map between Internet - and Ethernet addresses on the local network.</p> -<p class="Pp">The interface software implements an exponential backoff algorithm - when notified of a collision on the cable. This algorithm uses a 16-bit mask - and the VAX-11's interval timer in calculating a series of random backoff - values. The algorithm is as follows:</p> -<ol class="Bl-enum Bd-indent"> - <li>Initialize the mask to be all 1's.</li> - <li>If the mask is zero, 16 retries have been made and we give up.</li> - <li>Shift the mask left one bit and formulate a backoff by masking the - interval timer with the smaller of the complement of this mask and a 5-bit - mask, resulting in a pseudo-random number between 0 and 31. This produces - the number of slot times to delay, where a slot is 51 microseconds.</li> - <li>Use the value calculated in step 3 to delay before retransmitting the - packet. The delay is done in a software busy loop.</li> -</ol> -</section> -<section class="Sh"> -<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1> -<dl class="Bl-diag"> - <dt>ec%d: send error.</dt> - <dd>After 16 retransmissions using the exponential backoff algorithm described - above, the packet was dropped.</dd> - <dt>ec%d: input error (offset=%d).</dt> - <dd>The hardware indicated an error in reading a packet off the cable or an - illegally sized packet. The buffer offset value is printed for debugging - purposes.</dd> - <dt>ec%d: can't handle af%d.</dt> - <dd>The interface was handed a message with addresses formatted in an - unsuitable address family; the packet was dropped.</dd> -</dl> -</section> -<section class="Sh"> -<h1 class="Sh" id="SEE_ALSO"><a class="permalink" href="#SEE_ALSO">SEE - ALSO</a></h1> -<p class="Pp"><a class="Xr">arp(4)</a>, <a class="Xr">inet(4)</a>, - <a class="Xr">netintro(4)</a></p> -</section> -<section class="Sh"> -<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1> -<p class="Pp">The <code class="Nm">ec</code> driver appeared in - <span class="Ux">4.2BSD</span>.</p> -</section> -<section class="Sh"> -<h1 class="Sh" id="BUGS"><a class="permalink" href="#BUGS">BUGS</a></h1> -<p class="Pp">The hardware is not capable of talking to itself. The software - implements local sending and broadcast by sending such packets to the loop - interface. This is a kludge.</p> -<p class="Pp">Backoff delays are done in a software busy loop. This can degrade - the system if the network experiences frequent collisions.</p> -</section> -</div> -<table class="foot"> - <tr> - <td class="foot-date">February 5, 2019</td> - <td class="foot-os">NetBSD 10.1</td> - </tr> -</table> |