xref: /netbsd-src/share/man/man4/man4.vax/il.4 (revision 5f7096188587a2c7c95fa3c69b78e1ec9c7923d0)
1.\" Copyright (c) 1983, 1991 The Regents of the University of California.
2.\" All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\"    notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\"    notice, this list of conditions and the following disclaimer in the
11.\"    documentation and/or other materials provided with the distribution.
12.\" 3. All advertising materials mentioning features or use of this software
13.\"    must display the following acknowledgement:
14.\"	This product includes software developed by the University of
15.\"	California, Berkeley and its contributors.
16.\" 4. Neither the name of the University nor the names of its contributors
17.\"    may be used to endorse or promote products derived from this software
18.\"    without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\"     from: @(#)il.4	6.7 (Berkeley) 3/27/91
33.\"	$Id: il.4,v 1.2 1993/08/01 07:36:14 mycroft Exp $
34.\"
35.Dd March 27, 1991
36.Dt IL 4 vax
37.Os BSD 4.2
38.Sh NAME
39.Nm il
40.Nd Interlan NI1010 10 Mb/s Ethernet interface
41.Sh SYNOPSIS
42.Cd "device il0 at uba0 csr 164000 vector ilrint ilcint"
43.Sh DESCRIPTION
44The
45.Nm il
46interface provides access to a 10 Mb/s Ethernet network through
47an Interlan 1010 or 1010A controller.
48.Pp
49Each of the host's network addresses
50is specified at boot time with an
51.Dv SIOCSIFADDR
52.Xr ioctl 2 .
53The
54.Nm il
55interface employs the address resolution protocol described in
56.Xr arp 4
57to dynamically map between Internet and Ethernet addresses on the local
58network.
59.Pp
60The interface normally tries to use a ``trailer'' encapsulation
61to minimize copying data on input and output.
62The use of trailers is negotiated with
63.Tn ARP .
64This negotiation may be disabled, on a per-interface basis,
65by setting the
66.Dv IFF_NOTRAILERS
67flag with an
68.Dv SIOCSIFFLAGS
69.Xr ioctl .
70.Sh DIAGNOSTICS
71.Bl -diag
72.It il%d: input error.
73The hardware indicated an error
74in reading a packet off the cable or an illegally sized packet.
75.Pp
76.It il%d: can't handle af%d.
77The interface was handed
78a message with addresses formatted in an unsuitable address
79family; the packet was dropped.
80.Pp
81.It il%d: setaddr didn't work.
82The interface was unable to reprogram
83its physical ethernet address.
84This may happen with very early models of the interface.
85This facility is used only when
86the controller is not the first network interface configured for
87.Tn XNS .
88The oldest interface tested (2.7.1.0.1.45) has never failed in this way.
89.Pp
90.It il%d: reset failed, csr=%b.
91.It il%d: status failed, csr=%b.
92.It il%d: hardware diag failed, csr=%b.
93.It il%d: verifying setaddr, csr=%b.
94.It il%d: stray xmit interrupt, csr=%b.
95.It il%d: can't initialize.
96The above messages indicate a probable hardware error performing
97the indicated operation during autoconfiguration or initialization.
98The status field in the control and status register (the low-order four bits)
99should indicate the nature of the failure.
100See the hardware manual for details.
101.El
102.Sh SEE ALSO
103.Xr netintro 4 ,
104.Xr inet 4 ,
105.Xr arp 4
106.Sh HISTORY
107The
108.Nm
109interface appeared in
110.Bx 4.2 .
111