blob: 7117967591a9f60b6e4f8a3bed5fefd748a1ed27 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
|
<table class="head">
<tr>
<td class="head-ltitle">EX(4)</td>
<td class="head-vol">Device Drivers Manual (vax)</td>
<td class="head-rtitle">EX(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">ex</code> — <span class="Nd">Excelan 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">ex0 at uba0 csr 164000 vector excdint</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">ex</code> interface provides access to a 10
Mb/s Ethernet network through an Excelan controller used as a link-layer
interface.</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">ex</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>
</section>
<section class="Sh">
<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1>
<dl class="Bl-diag">
<dt>ex%d: HW %c.%c, NX %c.%c, hardware address %s.</dt>
<dd>This provides firmware revisions levels, and is expected during
autoconfiguration.</dd>
<dt>ex%d: can't initialize.</dt>
<dd>There was a failure in allocating UNIBUS resources for the device.</dd>
<dt>ex%d: configuration failed; cc = %x.</dt>
<dd>The hardware indicated an error when trying to initialize itself. The
error code returned is described at length in the device Reference
Manual.</dd>
<dt>ex%d: receive error %b.</dt>
<dd>The hardware indicated an error in reading a packet from the cable.
Specific Error bits are provided</dd>
<dt>ex%d: transmit error %b.</dt>
<dd>The hardware indicated an error in transmitting a packet to the cable or
an illegally sized packet. Specific Error bits are provided</dd>
<dt>ex%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">ex</code> driver appeared in
<span class="Ux">4.3BSD</span>.</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>
|