blob: 41c67c9154fc23e50fee3cced95df2568b70026e (
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
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
|
<table class="head">
<tr>
<td class="head-ltitle">NP(4)</td>
<td class="head-vol">Device Drivers Manual (vax)</td>
<td class="head-rtitle">NP(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">np</code> — <span class="Nd">Interlan
Np100 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">np0 at uba0 csr 166000 vector npintr</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">np</code> device provides access to an
Interlan Np100 Ethernet interface for control functions.</p>
<p class="Pp">This interface is unusual in that it requires loading firmware
into the controller before it may be used as a network link-level interface.
This is accomplished by opening a character special device, and writing data
to it. It is also possible to do post-mortem debugging of firmware failures
by reading the local memory of the device.</p>
<p class="Pp">Multiple control processes are allowed by opening separate minor
devices; secondary interfaces are specified by shifting the interface number
by 4 bits.</p>
<p class="Pp">The device also responds to commands passed through the driver by
the following <a class="Xr">ioctl(2)</a>s:</p>
<dl class="Bl-tag">
<dt id="NPRESET"><a class="permalink" href="#NPRESET"><code class="Dv">NPRESET</code></a></dt>
<dd>kills off all active network processes.</dd>
<dt id="NPSTART"><a class="permalink" href="#NPSTART"><code class="Dv">NPSTART</code></a></dt>
<dd>begins execution of the board at the specified address (usually
<code class="Li">0x400</code>).</dd>
<dt id="NPNETBOOT"><a class="permalink" href="#NPNETBOOT"><code class="Dv">NPNETBOOT</code></a></dt>
<dd>downloads the image from a server on the network. [Contact MICOM-INTERLAN
for details.]</dd>
</dl>
</section>
<section class="Sh">
<h1 class="Sh" id="DIAGNOSTICS"><a class="permalink" href="#DIAGNOSTICS">DIAGNOSTICS</a></h1>
<dl class="Bl-diag">
<dt>np%d: Bad Maintenance command: %x!</dt>
<dd>An invalid <a class="Xr">ioctl(2)</a> was passed to the np driver.</dd>
<dt>np%d: Panic NP100 bad buffer chain.</dt>
<dd>An error occurred in an read or write operation causing it to run out of
buffers before it finished the operation. This indicates a kernel failure
rather than a device failure.</dd>
<dt>NP100 unit %d not found!</dt>
<dd>A failure occurred during initialization, such that the UNIBUS address
expected for the board was found to be bad. Probably indicates hardware
problems with the board, as do the following:
<div class="Bd Bd-indent Li">
<pre>NP100 Unit %d timed out!
NP100 Unit %d Failed diagnostics!
Status from CSR0: %x.</pre>
</div>
</dd>
<dt>Panic from NP100 unit %d!</dt>
<dd></dd>
<dt>Panic Message: %s.</dt>
<dd>An occurrence on the board was deemed serious enough to have the VAX print
it out.</dd>
<dt>NP100 unit #%d available!</dt>
<dd>The board was successfully loaded and started.</dd>
<dt>np%d: Bad Req: %x.</dt>
<dd>The board made a maintenance request to the VAX that it did not
understand.</dd>
<dt>np%d: No more room on Command Queue!</dt>
<dd>The np driver allowed an internal resource to be exhausted. This should
never happen.</dd>
</dl>
<p class="Pp">There are 110 other diagnostic messages that can be enabled by
setting bits in a debugging mask. Consult the driver for details.</p>
</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>, <a class="Xr">vax/ix(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">np</code> driver appeared in
<span class="Ux">4.3BSD</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>
|
