|
|
1.1 root 1: .\" Copyright (c) 1986 Regents of the University of California.
2: .\" All rights reserved. The Berkeley software License Agreement
3: .\" specifies the terms and conditions for redistribution.
4: .\"
5: .\" @(#)np.4 6.3 (Berkeley) 5/21/86
6: .\"
7: .TH NP 4 "May 21, 1986"
8: .UC 5
9: .SH NAME
10: np \- Interlan Np100 10 Mb/s Ethernet interface
11: .SH SYNOPSIS
12: .B "device np0 at uba0 csr 166000 vector npintr"
13: .SH DESCRIPTION
14: The
15: .I NP
16: device provides access to an Interlan Np100 Ethernet interface
17: for control functions.
18: .PP
19: This interface is unusual in that it requires loading firmware
20: into the controller before it may be used as a network link-level interface.
21: This is accomplished by opening a character special device,
22: and writing data to it.
23: It is also possible to do post-mortem debugging of firmware failures
24: by reading the local memory of the device.
25: .PP
26: A program to load the image is provided in /usr/src/new/np100.
27: The sequence of commands would be:
28: .nf
29:
30: # ./npload np.image [/dev/np00]
31: # sleep 10
32: # ifconfig ix0 ...
33: .fi
34: .PP
35: Multiple control processes are allowed by opening separate
36: minor devices; secondary interfaces are specified by shifting
37: the interface number by 4 bits.
38: .PP
39: The device also responds to commands passed through the driver
40: by the following ioctls:
41: .TP
42: NPRESET
43: .br
44: kills off all active network processes.
45: .TP
46: NPSTART
47: .br
48: begins execution of the board at the specified address (usually 0x400).
49: .TP
50: NPNETBOOT
51: .br
52: downloads the image from a server on the network.
53: [Contact MICOM-INTERLAN for details.]
54: .SH DIAGNOSTICS
55: \fBnp%d: Bad Maintenance command: %x!\fP.
56: An invalid ioctl was passed to the np driver.
57: .PP
58: \fBnp%d: Panic NP100 bad buffer chain\fP.
59: An error occurred in an read or write operation causing it to
60: run out of buffers before it finished the operation.
61: This indicates a kernel failure rather than a device failure.
62: .PP
63: \fBNP100 unit %d not found!\fP.
64: A failure occurred during initialization, such that the unibus
65: address expected for the board was found to be bad.
66: Probably indicates hardware problems with the board, as do the following:
67: \fB
68: .nf
69:
70: NP100 Unit %d timed out!
71:
72: NP100 Unit %d Failed diagnostics!
73: Status from CSR0: %x.\fP
74: .fi
75: .PP
76: \fBPanic from NP100 unit %d!\\nPanic Message: %s\fP.
77: An occurrence on the board was deemed serious enough
78: to have the vax print it out.
79: .PP
80: \fBNP100 unit #%d available!\fP.
81: The board was successfully loaded and started.
82: .PP
83: \fBnp%d: Bad Req: %x.\fP.
84: The board made a maintenance request to the vax that it did not
85: understand.
86: .PP
87: \fBnp%d: No more room on Command Queue!\fP.
88: The np driver allowed an internal resource to be exhausted.
89: This should never happen.
90: .PP
91: There are 110 other diagnostic messages that can be enabled
92: by setting bits in a debugging mask.
93: Consult the driver for details.
94: .SH SEE ALSO
95: intro(4N), inet(4F), arp(4P), ix(4)
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.