xref: /netbsd-src/share/man/man4/man4.vax/np.4 (revision ce0bb6e8d2e560ecacbe865a848624f94498063b)
1.\" Copyright (c) 1986, 1991 The Regents of the University of California.
2.\" 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.\"     from: @(#)np.4	6.6 (Berkeley) 3/27/91
33.\"	$Id: np.4,v 1.2 1993/08/01 07:36:06 mycroft Exp $
34.\"
35.Dd March 27, 1991
36.Dt NP 4 vax
37.Os BSD 4.2
38.Sh NAME
39.Nm np
40.Nd Interlan Np100 10 Mb/s Ethernet interface
41.Sh SYNOPSIS
42.Cd "device np0 at uba0 csr 166000 vector npintr"
43.Sh DESCRIPTION
44The
45.Nm np
46device provides access to an Interlan Np100 Ethernet interface
47for control functions.
48.Pp
49This interface is unusual in that it requires loading firmware
50into the controller before it may be used as a network link-level interface.
51This is accomplished by opening a character special device,
52and writing data to it.
53It is also possible to do post-mortem debugging of firmware failures
54by reading the local memory of the device.
55.\" .Pp
56.\" A program to load the image is provided in
57.\" .Pa /usr/src/new/np100 .
58.\" The sequence of commands would be:
59.\" .Bd -literal -offset indent
60.\" # ./npload np.image [/dev/np00]
61.\" # sleep 10
62.\" # ifconfig ix0 ...
63.\" .Ed
64.Pp
65Multiple control processes are allowed by opening separate
66minor devices; secondary interfaces are specified by shifting
67the interface number by 4 bits.
68.Pp
69The device also responds to commands passed through the driver
70by the following
71.Xr ioctl 2 Ns s :
72.Bl -tag -width NPNETBOOT
73.It Dv NPRESET
74kills off all active network processes.
75.It Dv NPSTART
76begins execution of the board at the specified address (usually
77.Li 0x400 ) .
78.It Dv NPNETBOOT
79downloads the image from a server on the network.
80[Contact
81.Tn MICOM-INTERLAN
82for details.]
83.El
84.Sh DIAGNOSTICS
85.Bl -diag
86.It np%d: Bad Maintenance command: %x!
87An invalid
88.Xr ioctl
89was passed to the np driver.
90.Pp
91.It np%d: Panic NP100 bad buffer chain.
92An error occurred in an read or write operation causing it to
93run out of buffers before it finished the operation.
94This indicates a kernel failure rather than a device failure.
95.Pp
96.It NP100 unit %d not found!
97A failure occurred during initialization, such that the unibus
98address expected for the board was found to be bad.
99Probably indicates hardware problems with the board, as do the following:
100.Pp
101.Bd -filled -offset indent -compact
102.It NP100 Unit %d timed out!
103.It NP100 Unit %d Failed diagnostics!
104.It Status from CSR0: %x.
105.Ed
106.Pp
107.It "Panic from NP100 unit %d!"
108.It "Panic Message: %s."
109An occurrence on the board was deemed serious enough
110to have the vax print it out.
111.Pp
112.It NP100 unit #%d available!
113The board was successfully loaded and started.
114.Pp
115.It np%d: Bad Req: %x.
116The board made a maintenance request to the vax that it did not
117understand.
118.Pp
119.It np%d: No more room on Command Queue!
120The np driver allowed an internal resource to be exhausted.
121This should never happen.
122.El
123.Pp
124There are 110 other diagnostic messages that can be enabled
125by setting bits in a debugging mask.
126Consult the driver for details.
127.Sh SEE ALSO
128.Xr netintro 4 ,
129.Xr inet 4 ,
130.Xr arp 4 ,
131.Xr ix 4
132.Sh HISTORY
133The
134.Nm
135driver appeared in
136.Bx 4.3 .
137