blob: d0f33e9baf364fac67ed7c9bb4474764d716dcc6 (
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
|
<table class="head">
<tr>
<td class="head-ltitle">ENIC(4)</td>
<td class="head-vol">Device Drivers Manual</td>
<td class="head-rtitle">ENIC(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">enic</code> — <span class="Nd">eMIPS
ExtensibleNIC Ethernet interface driver</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">enic* at ebus0 addr ?</code></p>
</section>
<section class="Sh">
<h1 class="Sh" id="DESCRIPTION"><a class="permalink" href="#DESCRIPTION">DESCRIPTION</a></h1>
<p class="Pp">The <code class="Nm">enic</code> interface provides access to an
Ethernet network via the eMIPS builtin eNIC (Extensible Network Interface
Controller - Ethernet) 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">enic</code> interface employs the Address Resolution
Protocol (ARP) described in <a class="Xr">arp(4)</a> to dynamically map
between Internet and Ethernet addresses on the local network.</p>
<p class="Pp">Multicast Ethernet frames are unconditionally received and must be
filtered in software.</p>
</section>
<section class="Sh">
<h1 class="Sh" id="HARDWARE"><a class="permalink" href="#HARDWARE">HARDWARE</a></h1>
<section class="Ss">
<h2 class="Ss" id="emips"><a class="permalink" href="#emips">emips</a></h2>
<p class="Pp">The ENIC interface is present on the BEE3 and Xilinx XUP boards.
The interface speed is wired at 1Gbps.</p>
</section>
</section>
<section class="Sh">
<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1>
<dl class="Bl-diag">
<dt>enic%d: enic_put: no mem?</dt>
<dd>The driver could not allocate a transmit buffer, packet was not sent.</dd>
<dt>enic%d: internal error</dt>
<dd>This and other messages are indicative of bad hardware or software driver
coding errors.</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">emips/intro(4)</a>,
<a class="Xr">ifmedia(4)</a>, <a class="Xr">inet(4)</a>,
<a class="Xr">ifconfig(8)</a></p>
</section>
<section class="Sh">
<h1 class="Sh" id="HISTORY"><a class="permalink" href="#HISTORY">HISTORY</a></h1>
<p class="Pp"><code class="Nm">enic</code> driver first appeared in
<span class="Ux">NetBSD 6.0</span>.</p>
</section>
</div>
<table class="foot">
<tr>
<td class="foot-date">February 17, 2017</td>
<td class="foot-os">NetBSD 10.1</td>
</tr>
</table>
|