xref: /dragonfly/share/man/man4/ste.4 (revision ed5d5720)
1.\" Copyright (c) 1997, 1998, 1999
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: src/share/man/man4/ste.4,v 1.7.2.5 2003/02/17 21:20:39 trhodes Exp $
32.\" $DragonFly: src/share/man/man4/ste.4,v 1.6 2008/05/02 02:05:05 swildner Exp $
33.\"
34.Dd August 21, 1999
35.Dt STE 4
36.Os
37.Sh NAME
38.Nm ste
39.Nd "Sundance Technologies ST201 fast ethernet device driver"
40.Sh SYNOPSIS
41.Cd "device miibus"
42.Cd "device ste"
43.Sh DESCRIPTION
44The
45.Nm
46driver provides support for PCI ethernet adapters and embedded
47controllers based on the Sundance Technologies ST201 PCI fast
48ethernet controller chip.
49This includes the D-Link DFE-550TX.
50.Pp
51The Sundance ST201 uses bus master DMA and is designed to be a
523Com Etherlink XL workalike.
53It uses the same DMA descriptor
54structure and is very similar in operation, however its register
55layout is different.
56The ST201 has a 64-bit multicast hash filter
57and a single perfect filter entry for the station address.
58It supports both 10 and 100Mbps speeds in either full or half duplex
59using an MII transceiver.
60.Pp
61The
62.Nm
63driver supports the following media types:
64.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
65.It autoselect
66Enable autoselection of the media type and options.
67The user can manually override
68the autoselected mode by adding media options to the
69.Pa /etc/rc.conf
70file.
71.It 10baseT/UTP
72Set 10Mbps operation.
73The
74.Ar mediaopt
75option can also be used to select either
76.Ar full-duplex
77or
78.Ar half-duplex
79modes.
80.It 100baseTX
81Set 100Mbps (fast ethernet) operation.
82The
83.Ar mediaopt
84option can also be used to select either
85.Ar full-duplex
86or
87.Ar half-duplex
88modes.
89.El
90.Pp
91The
92.Nm
93driver supports the following media options:
94.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
95.It full-duplex
96Force full duplex operation
97.It half-duplex
98Force half duplex operation.
99.El
100.Pp
101For more information on configuring this device, see
102.Xr ifconfig 8 .
103.Sh DIAGNOSTICS
104.Bl -diag
105.It "ste%d: couldn't map ports/memory"
106A fatal initialization error has occurred.
107.It "ste%d: couldn't map interrupt"
108A fatal initialization error has occurred.
109.It "ste%d: watchdog timeout"
110The device has stopped responding to the network, or there is a problem with
111the network connection (cable).
112.It "ste%d: no memory for rx list"
113The driver failed to allocate an mbuf for the receiver ring.
114.It "ste%d: 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.It "ste%d: chip is in D3 power state -- setting to D0"
118This message applies only to adapters which support power
119management.
120Some operating systems place the controller in low power
121mode when shutting down, and some PCI BIOSes fail to bring the chip
122out of this state before configuring it.
123The controller loses all of
124its PCI configuration in the D3 state, so if the BIOS does not set
125it back to full power mode in time, it won't be able to configure it
126correctly.
127The driver tries to detect this condition and bring
128the adapter back to the D0 (full power) state, but this may not be
129enough to return the driver to a fully operational condition.
130If
131you see this message at boot time and the driver fails to attach
132the device as a network interface, you will have to perform a second
133warm boot to have the device properly configured.
134.Pp
135Note that this condition only occurs when warm booting from another
136operating system.
137If you power down your system prior to booting
138.Dx ,
139the card should be configured correctly.
140.El
141.Sh SEE ALSO
142.Xr arp 4 ,
143.Xr ifmedia 4 ,
144.Xr miibus 4 ,
145.Xr netintro 4 ,
146.Xr ng_ether 4 ,
147.Xr ifconfig 8
148.Rs
149.%T Sundance ST201 data sheet
150.%O http://www.sundanceti.com
151.Re
152.Sh HISTORY
153The
154.Nm
155device driver first appeared in
156.Fx 3.0 .
157.Sh AUTHORS
158The
159.Nm
160driver was written by
161.An Bill Paul Aq wpaul@ee.columbia.edu .
162