xref: /netbsd-src/share/man/man4/man4.vax/np.4 (revision cda4f8f6ee55684e8d311b86c99ea59191e6b74f)
1.\" Copyright (c) 1986, 1991, 1993
2.\"	The Regents of the University of California.  All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\"    notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\"    notice, this list of conditions and the following disclaimer in the
11.\"    documentation and/or other materials provided with the distribution.
12.\" 3. All advertising materials mentioning features or use of this software
13.\"    must display the following acknowledgement:
14.\"	This product includes software developed by the University of
15.\"	California, Berkeley and its contributors.
16.\" 4. Neither the name of the University nor the names of its contributors
17.\"    may be used to endorse or promote products derived from this software
18.\"    without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\"     @(#)np.4	8.1 (Berkeley) 6/5/93
33.\"
34.Dd June 5, 1993
35.Dt NP 4 vax
36.Os BSD 4.2
37.Sh NAME
38.Nm np
39.Nd Interlan Np100 10 Mb/s Ethernet interface
40.Sh SYNOPSIS
41.Cd "device np0 at uba0 csr 166000 vector npintr"
42.Sh DESCRIPTION
43The
44.Nm np
45device provides access to an Interlan Np100 Ethernet interface
46for control functions.
47.Pp
48This interface is unusual in that it requires loading firmware
49into the controller before it may be used as a network link-level interface.
50This is accomplished by opening a character special device,
51and writing data to it.
52It is also possible to do post-mortem debugging of firmware failures
53by reading the local memory of the device.
54.\" .Pp
55.\" A program to load the image is provided in
56.\" .Pa /usr/src/new/np100 .
57.\" The sequence of commands would be:
58.\" .Bd -literal -offset indent
59.\" # ./npload np.image [/dev/np00]
60.\" # sleep 10
61.\" # ifconfig ix0 ...
62.\" .Ed
63.Pp
64Multiple control processes are allowed by opening separate
65minor devices; secondary interfaces are specified by shifting
66the interface number by 4 bits.
67.Pp
68The device also responds to commands passed through the driver
69by the following
70.Xr ioctl 2 Ns s :
71.Bl -tag -width NPNETBOOT
72.It Dv NPRESET
73kills off all active network processes.
74.It Dv NPSTART
75begins execution of the board at the specified address (usually
76.Li 0x400 ) .
77.It Dv NPNETBOOT
78downloads the image from a server on the network.
79[Contact
80.Tn MICOM-INTERLAN
81for details.]
82.El
83.Sh DIAGNOSTICS
84.Bl -diag
85.It np%d: Bad Maintenance command: %x!
86An invalid
87.Xr ioctl
88was passed to the np driver.
89.Pp
90.It np%d: Panic NP100 bad buffer chain.
91An error occurred in an read or write operation causing it to
92run out of buffers before it finished the operation.
93This indicates a kernel failure rather than a device failure.
94.Pp
95.It NP100 unit %d not found!
96A failure occurred during initialization, such that the unibus
97address expected for the board was found to be bad.
98Probably indicates hardware problems with the board, as do the following:
99.Pp
100.Bd -filled -offset indent -compact
101.It NP100 Unit %d timed out!
102.It NP100 Unit %d Failed diagnostics!
103.It Status from CSR0: %x.
104.Ed
105.Pp
106.It "Panic from NP100 unit %d!"
107.It "Panic Message: %s."
108An occurrence on the board was deemed serious enough
109to have the vax print it out.
110.Pp
111.It NP100 unit #%d available!
112The board was successfully loaded and started.
113.Pp
114.It np%d: Bad Req: %x.
115The board made a maintenance request to the vax that it did not
116understand.
117.Pp
118.It np%d: No more room on Command Queue!
119The np driver allowed an internal resource to be exhausted.
120This should never happen.
121.El
122.Pp
123There are 110 other diagnostic messages that can be enabled
124by setting bits in a debugging mask.
125Consult the driver for details.
126.Sh SEE ALSO
127.Xr netintro 4 ,
128.Xr inet 4 ,
129.Xr arp 4 ,
130.Xr ix 4
131.Sh HISTORY
132The
133.Nm
134driver appeared in
135.Bx 4.3 .
136