1 .\" $NetBSD: ix.4,v 1.14 2003/04/06 19:33:58 wiz Exp $
3 .\" Copyright (c) 1986, 1991, 1993
4 .\" The Regents of the University of California. All rights reserved.
6 .\" Redistribution and use in source and binary forms, with or without
7 .\" modification, are permitted provided that the following conditions
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.
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
30 .\" from: @(#)ix.4 8.1 (Berkeley) 6/5/93
37 .Nd Interlan Np100 10 Mb/s Ethernet interface
39 .Cd "np0 at uba0 csr 166000 vector npintr"
41 NOTE: This driver has not been ported from
47 interface provides access to a 10 Mb/s Ethernet network through
48 an Interlan Np100 controller used as a link-layer interface.
50 This interface is unusual in that it requires loading firmware
51 into the controller before it may be used as a network interface.
52 This is accomplished by opening a character special device,
53 and writing data to it.
54 A program to load the image is provided in
55 .Pa /usr/src/new/np100 .
56 The sequence of commands would be:
57 .Bd -literal -offset indent
58 # ./npload np.image [/dev/np\*[Lt]board #\*[Gt] if other than np00]
63 Each of the host's network addresses
64 is specified at boot time with an
69 interface employs the address resolution protocol described in
71 to dynamically map between Internet and Ethernet addresses on the local
74 The interface normally tries to use a
77 to minimize copying data on input and output.
78 The use of trailers is negotiated with
80 This negotiation may be disabled, on a per-interface basis,
88 .It "ix%d: Req failed, cmd %x, stat %x, ust error %x,%x."
89 The firmware in the controller refused to honor a request from
91 in initializing packet level communications.
92 The board may need to be reset and reloaded.
93 Or, you may not have allowed enough time between loading the board
94 and issuing the request to begin
98 .It ix%d: can't initialize.
99 The interface was unable to obtain UNIBUS resources required for operation.
101 .It ix%d: failed to reinitialize DLA module.
102 The interface got sick after attempting to reprogram its physical
103 Ethernet address. Try reloading the firmware.
104 The attempt is made only when this interfaces is not the first
108 .It ix%d: can't handle af%d.
109 The interface was handed
110 a message with addresses formatted in an unsuitable address
111 family; the packet was dropped.
113 .It ix%d: stray xmit interrupt, npreq=%x.
114 This may happen if the board is reloaded while network processes are still
117 .It ixrint: cqe error %x, %x, %x.
118 This will result if an
120 request is made at an inopportune time, such as not allowing
121 enough time after loading the firmware.
122 After 100 such errors are logged, the
125 shut itself down, saying:
127 .It ixrint: shutting down unix dla.
128 The recourse is to reload the firmware and allow more time.