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
37 .\" $FreeBSD: /repoman/r/ncvs/src/share/man/man4/le.4,v 1.2 2006/02/02 14:57:00 marius Exp $
38 .\" $DragonFly: src/share/man/man4/man4.i386/lnc.4,v 1.7 2008/05/02 02:05:06 swildner Exp $
45 .Nd AMD Am7900 LANCE and Am79C9xx PCnet Ethernet interface driver
51 driver provides support for the AMD family of Lance/PCnet Ethernet NICs
52 including the Am7990 and Am79C960.
56 driver also supports PCnet adapters based on the
58 family of chips, which are single-chip implementations of a
60 chip and a DMA engine.
61 This includes a superset of the
63 bus Ethernet chip sets supported by the
68 driver treats all of these
70 bus Ethernet chip sets as an
71 .Tn AMD Am79C970 PCnet-PCI
72 and does not support the additional features like the MII bus and burst mode of
73 .Tn AMD Am79C971 PCnet-FAST
74 and greater chip sets.
77 driver should be preferred for the latter.
81 driver supports reception and transmission of extended frames for
83 Selective reception of multicast Ethernet frames is provided by a 64-bit mask;
84 multicast destination addresses are hashed to a bit entry using the Ethernet
90 .\" bus Ethernet cards supported by the
94 .\" .Bl -bullet -compact
100 .\" .Tn Digital DEPCA
105 .\" bus Ethernet cards supported by the
109 .\" .Bl -bullet -compact
111 .\" .Tn SKNET Personal MC2
118 bus Ethernet chip sets supported by the
124 .Tn AMD Am53C974/Am79C970/Am79C974 PCnet-PCI
126 .Tn AMD Am79C970A PCnet-PCI II
128 .Tn AMD Am79C971 PCnet-FAST
130 .Tn AMD Am79C972 PCnet-FAST+
132 .Tn AMD Am79C973/Am79C975 PCnet-FAST III
134 .Tn AMD Am79C976 PCnet-PRO
136 .Tn AMD Am79C978 PCnet-Home
141 driver supports the following media types with these chip sets:
142 .Bl -tag -width xxxxxxxxxxxxxxxxxxxx
144 Enable autoselection of the media type.
148 Select AUI/BNC media.
151 The following media option is supported with these media types:
152 .Bl -tag -width xxxxxxxxxxxxxxxxxxxx
154 Select full duplex operation.
161 driver does not support selecting 100Mbps (Fast Ethernet) media types.
163 For further information on configuring media types and options, see
167 .It "lnc%d: overflow"
168 More packets came in from the Ethernet than there was space in the
172 .It "lnc%d: receive buffer error"
175 ran out of buffer space, packet dropped.
176 .It "lnc%d: lost carrier"
177 The Ethernet carrier disappeared during an attempt to transmit.
180 will finish transmitting the current packet,
181 but will not automatically retry transmission if there is a collision.
182 .It "lnc%d: excessive collisions, tdr %d"
183 The Ethernet was extremely busy or jammed,
184 outbound packets were dropped after 16 attempts to retransmit.
187 is the abbreviation of
188 .Qq Time Domain Reflectometry .
189 The optionally reported TDR value is an internal counter of the interval
190 between the start of a transmission and the occurrence of a collision.
191 This value can be used to determine the distance from the Ethernet tap to
192 the point on the Ethernet cable that is shorted or open (unterminated).
193 .It "lnc%d: dropping chained buffer"
194 A packet did not fit into a single receive buffer and was dropped.
197 driver allocates buffers large enough to receive maximum sized Ethernet
198 packets, this means some other station on the LAN transmitted a packet
199 larger than allowed by the Ethernet standard.
200 .It "lnc%d: transmit buffer error"
203 ran out of buffer space before finishing the transmission of a packet.
204 If this error occurs, the driver software has a bug.
205 .It "lnc%d: underflow"
208 ran out of buffer space before finishing the transmission of a packet.
209 If this error occurs, the driver software has a bug.
210 .It "lnc%d: controller failed to initialize"
211 Driver failed to start the
213 This is potentially a hardware failure.
214 .It "lnc%d: memory error"
215 RAM failed to respond within the timeout when the
217 wanted to read or write it.
218 This is potentially a hardware failure.
219 .It "lnc%d: receiver disabled"
222 was turned off due to an error.
223 .It "lnc%d: transmitter disabled"
224 The transmitter of the
226 was turned off due to an error.
239 driver first appeared in
247 which was in turn ported from
251 driver was derived from the
262 .An "Marius Strobl" Aq marius@FreeBSD.org
266 .An "Bill Marquette" Aq bill.marquette@gmail.com .
268 .\" The Am7990 Revision C chips have a bug which causes garbage to be inserted
269 .\" in front of the received packet occasionally.
270 .\" The work-around is to ignore packets with an invalid destination address
271 .\" (garbage will usually not match), by double-checking the destination
272 .\" address of every packet in the driver.
273 .\" This work-around can be enabled with the
274 .\" .Dv LANCE_REVC_BUG
278 .\" .Dv LANCE_REVC_BUG
281 .\" driver executes one or two calls to an inline Ethernet address comparison
282 .\" function for every received packet.
283 .\" There is one comparison for each unicast packet, and two comparisons for
284 .\" each broadcast packet.
286 .\" In summary, the cost of the LANCE_REVC_BUG option is:
287 .\" .Bl -enum -compact
289 .\" loss of multicast support, and
293 .\" instructions per received packet, sometimes sixteen, depending on both the
294 .\" processor, and the type of packet.
297 .\" Alas, the Am7990 chip is so old that
301 .\" the production information about it; pending a search elsewhere, we do not
302 .\" know how to identify the revision C chip from the date codes.