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