1.\" $NetBSD: np.4,v 1.17 2017/08/01 11:11: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. Neither the name of the University nor the names of its contributors 15.\" may be used to endorse or promote products derived from this software 16.\" without specific prior written permission. 17.\" 18.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND 19.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 20.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 21.\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE 22.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL 23.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS 24.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) 25.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT 26.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY 27.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF 28.\" SUCH DAMAGE. 29.\" 30.\" from: @(#)np.4 8.1 (Berkeley) 6/5/93 31.\" 32.Dd February 17, 2017 33.Dt NP 4 vax 34.Os 35.Sh NAME 36.Nm np 37.Nd Interlan Np100 10 Mb/s Ethernet interface 38.Sh SYNOPSIS 39.Cd "np0 at uba0 csr 166000 vector npintr" 40.Sh DESCRIPTION 41NOTE: This driver has not been ported from 42.Bx 4.4 43yet. 44.Pp 45The 46.Nm np 47device provides access to an Interlan Np100 Ethernet interface 48for control functions. 49.Pp 50This interface is unusual in that it requires loading firmware 51into the controller before it may be used as a network link-level interface. 52This is accomplished by opening a character special device, 53and writing data to it. 54It is also possible to do post-mortem debugging of firmware failures 55by reading the local memory of the device. 56.\" .Pp 57.\" A program to load the image is provided in 58.\" .Pa /usr/src/new/np100 . 59.\" The sequence of commands would be: 60.\" .Bd -literal -offset indent 61.\" # ./npload np.image [/dev/np00] 62.\" # sleep 10 63.\" # ifconfig ix0 ... 64.\" .Ed 65.Pp 66Multiple control processes are allowed by opening separate 67minor devices; secondary interfaces are specified by shifting 68the interface number by 4 bits. 69.Pp 70The device also responds to commands passed through the driver 71by the following 72.Xr ioctl 2 Ns s : 73.Bl -tag -width NPNETBOOT 74.It Dv NPRESET 75kills off all active network processes. 76.It Dv NPSTART 77begins execution of the board at the specified address (usually 78.Li 0x400 ) . 79.It Dv NPNETBOOT 80downloads the image from a server on the network. 81[Contact 82.Tn MICOM-INTERLAN 83for details.] 84.El 85.Sh DIAGNOSTICS 86.Bl -diag 87.It np%d: Bad Maintenance command: %x! 88An invalid 89.Xr ioctl 2 90was passed to the np driver. 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.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.Bd -literal -offset indent -compact 100NP100 Unit %d timed out! 101NP100 Unit %d Failed diagnostics! 102Status from CSR0: %x. 103.Ed 104.It "Panic from NP100 unit %d!" 105.It "Panic Message: %s." 106An occurrence on the board was deemed serious enough 107to have the VAX print it out. 108.It NP100 unit #%d available! 109The board was successfully loaded and started. 110.It np%d: Bad Req: %x. 111The board made a maintenance request to the VAX that it did not 112understand. 113.It np%d: No more room on Command Queue! 114The np driver allowed an internal resource to be exhausted. 115This should never happen. 116.El 117There are 110 other diagnostic messages that can be enabled 118by setting bits in a debugging mask. 119Consult the driver for details. 120.Sh SEE ALSO 121.Xr arp 4 , 122.Xr inet 4 , 123.Xr netintro 4 , 124.Xr vax/ix 4 125.Sh HISTORY 126The 127.Nm 128driver appeared in 129.Bx 4.3 . 130