xref: /freebsd/share/man/man4/xl.4 (revision 6b3455a7665208c366849f0b2b3bc916fb97516e)
1.\" Copyright (c) 1997, 1998
2.\"	Bill Paul <wpaul@ctr.columbia.edu>. 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 Bill Paul.
15.\" 4. Neither the name of the author nor the names of any co-contributors
16.\"    may be used to endorse or promote products derived from this software
17.\"   without specific prior written permission.
18.\"
19.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND
20.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
21.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
22.\" ARE DISCLAIMED.  IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD
23.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
24.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
25.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
26.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
27.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
28.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
29.\" THE POSSIBILITY OF SUCH DAMAGE.
30.\"
31.\" $FreeBSD$
32.\"
33.Dd July 28, 2004
34.Dt XL 4
35.Os
36.Sh NAME
37.Nm xl
38.Nd "3Com Etherlink XL and Fast Etherlink XL ethernet device driver"
39.Sh SYNOPSIS
40.Cd "device miibus"
41.Cd "device xl"
42.Sh DESCRIPTION
43The
44.Nm
45driver provides support for PCI ethernet adapters and embedded
46controllers based on the 3Com "boomerang," "cyclone," "hurricane"
47and "tornado" bus-master Etherlink XL chips.
48.Pp
49The Etherlink XL chips support built-in 10baseT, 10base2 and 10base5
50transceivers as well as an MII bus for externally attached PHY
51transceivers.
52The 3c905 series typically uses a National Semiconductor
53NS 83840A 10/100 PHY for 10/100 Mbps support in full or half-duplex.
54The 3c905B adapters have built-in autonegotiation logic mapped onto
55the MII for compatibility with previous drivers.
56Fast Etherlink XL
57adapters such as the 3c905-TX and 3c905B-TX are capable of 10 or
58100Mbps data rates in either full or half duplex and can be manually
59configured for any supported mode or automatically negotiate the highest
60possible mode with a link partner.
61.Sh HARDWARE
62The
63.Nm
64driver supports the following hardware:
65.Pp
66.Bl -bullet -compact
67.It
683c900-TPO
69.It
703c900-COMBO
71.It
723c905-TX
73.It
743c905-T4
75.It
763c900B-TPO
77.It
783c900B-TPC,
79.It
803c900B-FL,
81.It
823c900B-COMBO,
83.It
843c905B-T4,
85.It
863c905B-TX,
87.It
883c905B-FX,
89.It
903c905B-COMBO
91.It
923c905C-TX;
93.It
943c980, 3c980B, and 3c980C server adapters
95.It
963cSOHO100-TX OfficeConnect adapters
97.It
983c450 HomeConnect adapters
99.It
1003c555, 3c556 and 3c556B mini-PCI adapters
101.It
1023C3SH573BT, 3C575TX, 3CCFE575BT, 3CXFE575BT,  3CCFE575CT, 3CXFE575CT,
1033CCFEM656, 3CCFEM656B, and 3CCFEM656C, 3CXFEM656, 3CXFEM656B, and
1043CXFEM656C CardBus adapters
105.It
1063c905-TX, 3c905B-TX 3c905C-TX, and 3c920B-EMB embedded adapters
107.El
108.Pp
109The
110.Nm
111driver supports the following media types:
112.Pp
113.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
114.It autoselect
115Enable autoselection of the media type and options.
116Note that this
117option is only available with the 3c905 and 3c905B adapters with
118external PHYs or built-in autonegotiation logic.
119For 3c900 adapters,
120the driver will choose the mode specified in the EEPROM.
121The user can
122change this by adding media options to the
123.Pa /etc/rc.conf
124file.
125.It 10baseT/UTP
126Set 10Mbps operation.
127The
128.Ar mediaopt
129option can also be used to select either
130.Ar full-duplex
131or
132.Ar half-duplex
133modes.
134.It 100baseTX
135Set 100Mbps (fast ethernet) operation.
136The
137.Ar mediaopt
138option can also be used to select either
139.Ar full-duplex
140or
141.Ar half-duplex
142modes.
143.It 10base5/AUI
144Enable AUI transceiver (available only on COMBO cards).
145.It 10base2/BNC
146Enable BNC coax transceiver (available only on COMBO cards).
147.El
148.Pp
149The
150.Nm
151driver supports the following media options:
152.Pp
153.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
154.It full-duplex
155Force full duplex operation
156.It half-duplex
157Force half duplex operation.
158.El
159.Pp
160Note that the 100baseTX media type is only available if supported
161by the adapter.
162For more information on configuring this device, see
163.Xr ifconfig 8 .
164.Pp
165Both the 3C656 family of CardBus cards and the 3C556 family of MiniPCI
166cards have a built-in proprietary modem.
167Neither the
168.Nm
169driver nor any other
170.Fx
171driver supports this modem.
172.Sh DIAGNOSTICS
173.Bl -diag
174.It "xl%d: couldn't map memory"
175A fatal initialization error has occurred.
176.It "xl%d: couldn't map interrupt"
177A fatal initialization error has occurred.
178.It "xl%d: device timeout"
179The device has stopped responding to the network, or there is a problem with
180the network connection (cable).
181.It "xl%d: no memory for rx list"
182The driver failed to allocate an mbuf for the receiver ring.
183.It "xl%d: no memory for tx list"
184The driver failed to allocate an mbuf for the transmitter ring when
185allocating a pad buffer or collapsing an mbuf chain into a cluster.
186.It "xl%d: command never completed!"
187Some commands issued to the 3c90x ASIC take time to complete: the
188driver is supposed to wait until the 'command in progress' bit in
189the status register clears before continuing.
190In rare instances, this
191bit may not clear.
192To avoid getting caught in an infinite wait loop,
193the driver only polls the bit for a finite number of times before
194giving up, at which point it issues this message.
195This message may
196be printed during driver initialization on slower machines.
197If you
198see this message but the driver continues to function normally, the
199message can probably be ignored.
200.It "xl%d: chip is in D3 power state -- setting to D0"
201This message applies only to 3c905B adapters, which support power
202management.
203Some operating systems place the 3c905B in low power
204mode when shutting down, and some PCI BIOSes fail to bring the chip
205out of this state before configuring it.
206The 3c905B loses all of
207its PCI configuration in the D3 state, so if the BIOS does not set
208it back to full power mode in time, it won't be able to configure it
209correctly.
210The driver tries to detect this condition and bring
211the adapter back to the D0 (full power) state, but this may not be
212enough to return the driver to a fully operational condition.
213If
214you see this message at boot time and the driver fails to attach
215the device as a network interface, you will have to perform second
216warm boot to have the device properly configured.
217.Pp
218Note that this condition only occurs when warm booting from another
219operating system.
220If you power down your system prior to booting
221.Fx ,
222the card should be configured correctly.
223.It "xl%d: WARNING: no media options bits set in the media options register!"
224This warning may appear when using the driver on some Dell Latitude
225docking stations with built-in 3c905-TX adapters.
226For whatever the
227reason, the 'MII available' bit in the media options register on
228this particular equipment is not set, even though it should be (the
2293c905-TX always uses an external PHY transceiver).
230The driver will
231attempt to guess the proper media type based on the PCI device ID
232word.
233The driver makes a lot of noise about this condition because
234the author considers it a manufacturing defect.
235.El
236.Sh SEE ALSO
237.Xr arp 4 ,
238.Xr cardbus 4 ,
239.Xr miibus 4 ,
240.Xr netintro 4 ,
241.Xr ng_ether 4 ,
242.Xr pccard 4 ,
243.Xr ifconfig 8
244.Sh HISTORY
245The
246.Nm
247device driver first appeared in
248.Fx 3.0 .
249.Sh AUTHORS
250The
251.Nm
252driver was written by
253.An Bill Paul Aq wpaul@ctr.columbia.edu .
254