NP(4) BSD Programmer's Manual (VAX Architecture) NP(4) NNAAMMEE nnpp - Interlan Np100 10 Mb/s Ethernet interface SSYYNNOOPPSSIISS ddeevviiccee nnpp00 aatt uubbaa00 ccssrr 116666000000 vveeccttoorr nnppiinnttrr DDEESSCCRRIIPPTTIIOONN The nnpp device provides access to an Interlan Np100 Ethernet interface for control functions. This interface is unusual in that it requires loading firmware into the controller before it may be used as a network link-level interface. This is accomplished by opening a character special device, and writing data to it. It is also possible to do post-mortem debugging of firmware fail- ures by reading the local memory of the device. Multiple control processes are allowed by opening separate minor devices; secondary interfaces are specified by shifting the interface number by 4 bits. The device also responds to commands passed through the driver by the following ioctl(2)s: NPRESET kills off all active network processes. NPSTART begins execution of the board at the specified address (usual- ly 0x400). NPNETBOOT downloads the image from a server on the network. [Contact MICOM-INTERLAN for details.] DDIIAAGGNNOOSSTTIICCSS nnpp%%dd:: BBaadd MMaaiinntteennaannccee ccoommmmaanndd:: %%xx!! An invalid ioctl was passed to the np driver. nnpp%%dd:: PPaanniicc NNPP110000 bbaadd bbuuffffeerr cchhaaiinn.. An error occurred in an read or write operation causing it to run out of buffers before it finished the operation. This indicates a kernel failure rather than a device failure. NNPP110000 uunniitt %%dd nnoott ffoouunndd!! A failure occurred during initialization, such that the unibus address expected for the board was found to be bad. Probably indicates hardware problems with the board, as do the following: NNPP110000 UUnniitt %%dd ttiimmeedd oouutt!! NNPP110000 UUnniitt %%dd FFaaiilleedd ddiiaaggnnoossttiiccss!! SSttaattuuss ffrroomm CCSSRR00:: %%xx.. PPaanniicc ffrroomm NNPP110000 uunniitt %%dd!! PPaanniicc MMeessssaaggee:: %%ss.. An occurrence on the board was deemed serious enough to have the vax print it out. NNPP110000 uunniitt ##%%dd aavvaaiillaabbllee!! The board was successfully loaded and started. nnpp%%dd:: BBaadd RReeqq:: %%xx.. The board made a maintenance request to the vax that it did not understand. nnpp%%dd:: NNoo mmoorree rroooomm oonn CCoommmmaanndd QQuueeuuee!! The np driver allowed an internal resource to be exhausted. This should never happen. There are 110 other diagnostic messages that can be enabled by setting bits in a debugging mask. Consult the driver for details. SSEEEE AALLSSOO netintro(4), inet(4), arp(4), ix(4) HHIISSTTOORRYY The nnpp driver appeared in 4.3BSD. 4.2 Berkeley Distribution June 5, 1993 2