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