1 .\" $NetBSD: le.4,v 1.22 2004/10/04 19:12:52 rumble Exp $
4 .\" Copyright (c) 1992, 1993
5 .\" The Regents of the University of California. All rights reserved.
7 .\" This software was developed by the Computer Systems Engineering group
8 .\" at Lawrence Berkeley Laboratory under DARPA contract BG 91-66 and
9 .\" contributed to Berkeley.
11 .\" Redistribution and use in source and binary forms, with or without
12 .\" modification, are permitted provided that the following conditions
14 .\" 1. Redistributions of source code must retain the above copyright
15 .\" notice, this list of conditions and the following disclaimer.
16 .\" 2. Redistributions in binary form must reproduce the above copyright
17 .\" notice, this list of conditions and the following disclaimer in the
18 .\" documentation and/or other materials provided with the distribution.
19 .\" 3. Neither the name of the University nor the names of its contributors
20 .\" may be used to endorse or promote products derived from this software
21 .\" without specific prior written permission.
23 .\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
24 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
25 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
26 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
27 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
28 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
29 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
30 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
31 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
32 .\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
35 .\" from: Header: le.4,v 1.2 92/10/13 05:31:33 leres Exp
36 .\" from: @(#)le.4 8.1 (Berkeley) 6/9/93
44 .Nd "AMD Am7900 LANCE and Am79C9xx ILACC/PCnet Ethernet interface driver"
46 To compile this driver into the kernel,
47 place the following line in your
48 kernel configuration file:
49 .Bd -ragged -offset indent
53 Alternatively, to load the driver as a
54 module at boot time, place the following line in
56 .Bd -literal -offset indent
60 For ISA non-PnP adapters, the port address as well as the IRQ and the DRQ
61 numbers have to be specified in
62 .Pa /boot/device.hints :
63 .Cd hint.le.0.at="isa"
64 .Cd hint.le.0.port="0x280"
65 .Cd hint.le.0.irq="10"
70 driver provides support for Ethernet adapters based on the
74 .Pq CMOS, pin-compatible
75 Local Area Network Controller for Ethernet
81 driver also supports Ethernet adapters based on the
83 Integrated Local Area Communications Controller
87 family of chips, which are single-chip implementations of a
89 chip and a DMA engine.
90 This includes a superset of the
92 bus Ethernet chips supported by the
97 driver treats all of these
99 bus Ethernet chips as an
100 .Tn AMD Am79C970 PCnet-PCI
101 and does not support the additional features like the MII bus and burst mode of
102 .Tn AMD Am79C971 PCnet-FAST
106 driver should be preferred for the latter.
110 driver aims at supporting as many different chips on as many different
111 platforms as possible,
112 partially at the cost of the best performance with some of these.
116 driver supports reception and transmission of extended frames for
118 Selective reception of multicast Ethernet frames is provided by a 64-bit mask;
119 multicast destination addresses are hashed to a bit entry using the Ethernet
127 bus Ethernet adapters which are based on the following chips:
131 .Tn AMD Am7990 and Am79C90 LANCE
133 .Tn AMD Am79C960 PCnet-ISA
135 .Tn AMD Am79C961 PCnet-ISA+
137 .Tn AMD Am79C961A PCnet-ISA II
140 This includes support for the following Ethernet adapters:
148 .\" .Tn Digital DEPCA
157 .Tn AMD AM1500T/AM2100
163 .Tn Allied Telesyn AT-1500
165 .Tn Boca LANCard Combo
167 .Tn Cabletron E2100 Series DNI
169 .Tn Cabletron E2200 Single Chip
171 .Tn Melco Inc. LGY-IV
175 .Tn Racal InterLan EtherBlaster
180 driver does not support the selection of media types and options via
184 bus Ethernet adapters.
188 bus Ethernet chips supported by the
194 .Tn AMD Am53C974/Am79C970/Am79C974 PCnet-PCI
196 .Tn AMD Am79C970A PCnet-PCI II
198 .Tn AMD Am79C971 PCnet-FAST
200 .Tn AMD Am79C972 PCnet-FAST+
202 .Tn AMD Am79C973/Am79C975 PCnet-FAST III
204 .Tn AMD Am79C976 PCnet-PRO
206 .Tn AMD Am79C978 PCnet-Home
209 This includes support for the following Ethernet adapters:
215 .Tn Allied Telesyn AT-2450 and AT-2700 series
217 .Tn VMware emulated AMD Am79C970A PCnet-PCI II interface
222 driver supports the selection of the following media types via
226 bus Ethernet adapters:
227 .Bl -tag -width ".Cm 10base5/AUI"
229 Enable autoselection of the media type.
233 Select AUI/BNC media.
236 The following media option is supported with these media types:
237 .Bl -tag -width ".Cm full-duplex"
239 Select full duplex operation.
246 driver does not support selecting 100Mbps (Fast Ethernet) media types.
250 driver supports the on-board
257 driver allows the selection of the following media types via
259 with these on-board interfaces:
260 .Bl -tag -width ".Cm 10base5/AUI"
262 Enable autoselection of the media type.
269 When using autoselection, a default media type is selected for use by
270 examining all ports for carrier.
271 The first media type with which a carrier is detected will be selected.
272 Additionally, if carrier is dropped on a port, the driver will switch
273 between the possible ports until one with carrier is found.
277 driver also supports the following
279 Ethernet add-on adapters:
283 .Tn SCSI HBA and Buffered Ethernet
284 .Pq SBE/S, P/N 501-1869
286 .Tn Fast SCSI and Buffered Ethernet
287 .Pq FSBE/S, P/N 501-2015 and 501-2981
292 driver does not support the selection of media types and options via
296 Ethernet add-on adapters.
298 For further information on configuring media types and options, see
303 More packets came in from the Ethernet than there was space in the
307 .It "le%d: receive buffer error"
310 ran out of buffer space, packet dropped.
311 .It "le%d: lost carrier"
312 The Ethernet carrier disappeared during an attempt to transmit.
315 will finish transmitting the current packet,
316 but will not automatically retry transmission if there is a collision.
317 .It "le%d: excessive collisions, tdr %d"
318 The Ethernet was extremely busy or jammed,
319 outbound packets were dropped after 16 attempts to retransmit.
322 is the abbreviation of
323 .Qq Time Domain Reflectometry .
324 The optionally reported TDR value is an internal counter of the interval
325 between the start of a transmission and the occurrence of a collision.
326 This value can be used to determine the distance from the Ethernet tap to
327 the point on the Ethernet cable that is shorted or open (unterminated).
328 .It "le%d: dropping chained buffer"
329 A packet did not fit into a single receive buffer and was dropped.
332 driver allocates buffers large enough to receive maximum sized Ethernet
333 packets, this means some other station on the LAN transmitted a packet
334 larger than allowed by the Ethernet standard.
335 .It "le%d: transmit buffer error"
338 ran out of buffer space before finishing the transmission of a packet.
339 If this error occurs, the driver software has a bug.
340 .It "le%d: underflow"
343 ran out of buffer space before finishing the transmission of a packet.
344 If this error occurs, the driver software has a bug.
345 .It "le%d: controller failed to initialize"
346 Driver failed to start the
348 This is potentially a hardware failure.
349 .It "le%d: memory error"
350 RAM failed to respond within the timeout when the
352 wanted to read or write it.
353 This is potentially a hardware failure.
354 .It "le%d: receiver disabled"
357 was turned off due to an error.
358 .It "le%d: transmitter disabled"
359 The transmitter of the
361 was turned off due to an error.
374 driver was ported from
376 and first appeared in
380 version in turn was derived from the
382 driver which first appeared in
388 .An Marius Strobl Aq Mt marius@FreeBSD.org .
390 .\" The Am7990 Revision C chips have a bug which causes garbage to be inserted
391 .\" in front of the received packet occasionally.
392 .\" The work-around is to ignore packets with an invalid destination address
393 .\" (garbage will usually not match), by double-checking the destination
394 .\" address of every packet in the driver.
395 .\" This work-around can be enabled with the
396 .\" .Dv LANCE_REVC_BUG
400 .\" .Dv LANCE_REVC_BUG
403 .\" driver executes one or two calls to an inline Ethernet address comparison
404 .\" function for every received packet.
407 .\" it is exactly eight instructions of 16 bits each.
408 .\" There is one comparison for each unicast packet, and two comparisons for
409 .\" each broadcast packet.
411 .\" In summary, the cost of the LANCE_REVC_BUG option is:
412 .\" .Bl -enum -compact
414 .\" loss of multicast support, and
418 .\" instructions per received packet, sometimes sixteen, depending on both the
419 .\" processor, and the type of packet.
422 .\" All sun3 systems are presumed to have this bad revision of the Am7990,
423 .\" until proven otherwise.
424 .\" Alas, the only way to prove what revision of the chip is in a particular
425 .\" system is inspection of the date code on the chip package,
426 .\" to compare against a list of what chip revisions were fabricated between
429 .\" Alas, the Am7990 chip is so old that
433 .\" the production information about it; pending a search elsewhere, we do not
434 .\" know how to identify the revision C chip from the date codes.