Return to il.4 CVS log

Up to [CSRG BSD Unix] / 43BSDTahoe / man / man4 / vax

Annotation of 43BSDTahoe/man/man4/vax/il.4, revision 1.1.1.1

1.1       root        1: .\" Copyright (c) 1983 Regents of the University of California.
                      2: .\" All rights reserved.  The Berkeley software License Agreement
                      3: .\" specifies the terms and conditions for redistribution.
                      4: .\"
                      5: .\"    @(#)il.4        6.4 (Berkeley) 6/1/86
                      6: .\"
                      7: .TH IL 4 "June 1, 1986"
                      8: .UC 5
                      9: .SH NAME
                     10: il \- Interlan NI1010 10 Mb/s Ethernet interface
                     11: .SH SYNOPSIS
                     12: .B "device il0 at uba0 csr 164000 vector ilrint ilcint"
                     13: .SH DESCRIPTION
                     14: The
                     15: .I il
                     16: interface provides access to a 10 Mb/s Ethernet network through
                     17: an Interlan 1010 or 1010A controller.
                     18: .PP
                     19: Each of the host's network addresses
                     20: is specified at boot time with an SIOCSIFADDR
                     21: ioctl.  The
                     22: .I il
                     23: interface employs the address resolution protocol described in
                     24: .IR arp (4P)
                     25: to dynamically map between Internet and Ethernet addresses on the local
                     26: network.
                     27: .PP
                     28: The interface normally tries to use a ``trailer'' encapsulation
                     29: to minimize copying data on input and output.
                     30: The use of trailers is negotiated with ARP.
                     31: This negotiation may be disabled, on a per-interface basis,
                     32: by setting the IFF_NOTRAILERS
                     33: flag with an SIOCSIFFLAGS ioctl.
                     34: .SH DIAGNOSTICS
                     35: \fBil%d: input error\fP.  The hardware indicated an error
                     36: in reading a packet off the cable or an illegally sized packet.
                     37: .PP
                     38: \fBil%d: can't handle af%d\fP.  The interface was handed
                     39: a message with addresses formatted in an unsuitable address
                     40: family; the packet was dropped.
                     41: .PP
                     42: \fBil%d: setaddr didn't work\fP.  The interface was unable to reprogram
                     43: its physical ethernet address.
                     44: This may happen with very early models of the interface.
                     45: This facility is used only when
                     46: the controller is not the first network interface configured for XNS.
                     47: The oldest interface tested (2.7.1.0.1.45) has never failed in this way.
                     48: .PP
                     49: The following messages indicate a probable hardware error performing
                     50: the indicated operation during autoconfiguration or initialization.
                     51: The status field in the control and status register (the low-order four bits)
                     52: should indicate the nature of the failure.
                     53: See the hardware manual for details.
                     54: .PP
                     55: \fBil%d: reset failed, csr=%b\fP.
                     56: .PP
                     57: \fBil%d: status failed, csr=%b\fP.
                     58: .PP
                     59: \fBil%d: hardware diag failed, csr=%b\fP.
                     60: .PP
                     61: \fBil%d: verifying setaddr, csr=%b\fP.
                     62: .PP
                     63: \fBil%d: stray xmit interrupt, csr=%b\fP.
                     64: .PP
                     65: \fBil%d: can't initialize\fP.
                     66: .SH SEE ALSO
                     67: intro(4N), inet(4F), arp(4P)

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.