xref: /openbsd/share/man/man4/tl.4 (revision 3cab2bb3)
1.\"	$OpenBSD: tl.4,v 1.22 2013/07/16 16:05:49 schwarze Exp $
2.\"
3.\" Copyright (c) 1997, 1998
4.\"	Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved.
5.\"
6.\" Redistribution and use in source and binary forms, with or without
7.\" modification, are permitted provided that the following conditions
8.\" are met:
9.\" 1. Redistributions of source code must retain the above copyright
10.\"    notice, this list of conditions and the following disclaimer.
11.\" 2. Redistributions in binary form must reproduce the above copyright
12.\"    notice, this list of conditions and the following disclaimer in the
13.\"    documentation and/or other materials provided with the distribution.
14.\" 3. All advertising materials mentioning features or use of this software
15.\"    must display the following acknowledgement:
16.\"	This product includes software developed by Bill Paul.
17.\" 4. Neither the name of the author nor the names of any co-contributors
18.\"    may be used to endorse or promote products derived from this software
19.\"   without specific prior written permission.
20.\"
21.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND
22.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
23.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
24.\" ARE DISCLAIMED.  IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD
25.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
26.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF
27.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS
28.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN
29.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE)
30.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
31.\" THE POSSIBILITY OF SUCH DAMAGE.
32.\"
33.\"	$Id: tl.4,v 1.22 2013/07/16 16:05:49 schwarze Exp $
34.\"
35.Dd $Mdocdate: July 16 2013 $
36.Dt TL 4
37.Os
38.Sh NAME
39.Nm tl
40.Nd Texas Instruments ThunderLAN 10/100 Ethernet device
41.Sh SYNOPSIS
42.Cd "tl* at pci?"
43.Cd "lxtphy* at mii?"
44.Cd "mlphy* at mii?"
45.Cd "nsphy* at mii?"
46.Cd "tlphy* at mii?"
47.Sh DESCRIPTION
48The
49.Nm
50driver provides support for PCI Ethernet adapters based on the Texas
51Instruments ThunderLAN Ethernet controller chip.
52This includes a large number of Compaq PCI-bus Ethernet adapters as well as
53the integrated Ethernet controllers built in to several models
54of Compaq Prosignia servers and Compaq Deskpro desktop machines.
55This driver also supports the Olicom OC-2135/2138, OC-2325 and OC-2326
5610/100 TX UTP adapters and the Racore 8165 10/100baseTX and 8148
5710baseT/100baseTX/100baseFX multi-personality cards.
58.Pp
59The ThunderLAN controller has a standard MII interface that supports
60up to 32 physical interface devices (PHYs).
61It also has a built-in 10baseT PHY hardwired at MII address 31, which may be
62used in some 10Mbps-only hardware configurations.
63In 100Mbps configurations, a National Semiconductor DP83840A or other
64MII-compliant PHY may be attached to the ThunderLAN's MII bus.
65If a DP83840A or equivalent is available, the ThunderLAN chip can operate
66at either 100Mbps or 10Mbps in either half-duplex or full-duplex modes.
67The ThunderLAN's built-in PHY and the DP83840A also support autonegotiation.
68.Pp
69The
70.Nm
71driver supports the following media types:
72.Bl -tag -width full-duplex
73.It autoselect
74Enable autoselection of the media type and options.
75Note that this option is only available on those PHYs that support
76autonegotiation.
77Also, the PHY will not advertise those modes that have been explicitly
78disabled using the following media options.
79.It 10baseT
80Set 10Mbps operation.
81.It 100baseTX
82Set 100Mbps (Fast Ethernet) operation.
83.It 10base5
84Enable AUI/BNC interface (useful only with the built-in PHY).
85.El
86.Pp
87The
88.Nm
89driver supports the following media options:
90.Bl -tag -width full-duplex
91.It full-duplex
92Force full duplex operation.
93.It half-duplex
94Force half duplex operation.
95.It hw-loopback
96Enable hardware loopback mode.
97.El
98.Pp
99Note that the 100baseTX media type is only available if supported
100by the PHY.
101For more information on configuring this device, see
102.Xr ifconfig 8 .
103.Sh DIAGNOSTICS
104.Bl -diag
105.It "tl0: couldn't map memory"
106A fatal initialization error has occurred.
107.It "tl0: couldn't map interrupt"
108A fatal initialization error has occurred.
109.It "tl0: device timeout"
110The device has stopped responding to the network, or there is a problem with
111the network connection (cable).
112.It "tl0: no memory for rx list"
113The driver failed to allocate an mbuf for the receiver ring.
114.It "tl0: no memory for tx list"
115The driver failed to allocate an mbuf for the transmitter ring when
116allocating a pad buffer or collapsing an mbuf chain into a cluster.
117.El
118.Sh SEE ALSO
119.Xr arp 4 ,
120.Xr ifmedia 4 ,
121.Xr intro 4 ,
122.Xr lxtphy 4 ,
123.Xr mlphy 4 ,
124.Xr netintro 4 ,
125.Xr nsphy 4 ,
126.Xr pci 4 ,
127.Xr tlphy 4 ,
128.Xr hostname.if 5 ,
129.Xr ifconfig 8
130.Sh HISTORY
131The
132.Nm
133device driver first appeared in
134.Fx 2.2 .
135.Ox
136support first appeared in
137.Ox 2.4 .
138.Sh AUTHORS
139The
140.Nm
141driver was written by
142.An Bill Paul Aq Mt wpaul@ctr.columbia.edu .
143