xref: /freebsd/share/man/man4/ste.4 (revision 5ca8e32633c4ffbbcd6762e5888b6a4ba0708c6c)
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.Dd December 24, 2009
32.Dt STE 4
33.Os
34.Sh NAME
35.Nm ste
36.Nd "Sundance Technologies ST201 Fast Ethernet device driver"
37.Sh SYNOPSIS
38To compile this driver into the kernel,
39place the following lines in your
40kernel configuration file:
41.Bd -ragged -offset indent
42.Cd "device miibus"
43.Cd "device ste"
44.Ed
45.Pp
46Alternatively, to load the driver as a
47module at boot time, place the following line in
48.Xr loader.conf 5 :
49.Bd -literal -offset indent
50if_ste_load="YES"
51.Ed
52.Sh DESCRIPTION
53The
54.Nm
55driver provides support for PCI Ethernet adapters and embedded
56controllers based on the Sundance Technologies ST201 PCI Fast
57Ethernet controller chip.
58.Pp
59The Sundance ST201 uses bus master DMA and is designed to be a
603Com Etherlink XL workalike.
61It uses the same DMA descriptor
62structure and is very similar in operation, however its register
63layout is different.
64The ST201 has a 64-bit multicast hash filter
65and a single perfect filter entry for the station address.
66It supports both 10 and 100Mbps speeds in either full or half duplex
67using an MII transceiver.
68.Pp
69The
70.Nm
71driver supports the following media types:
72.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
73.It autoselect
74Enable autoselection of the media type and options.
75The user can manually override
76the autoselected mode by adding media options to the
77.Pa /etc/rc.conf
78file.
79.It 10baseT/UTP
80Set 10Mbps operation.
81The
82.Ar mediaopt
83option can also be used to select either
84.Ar full-duplex
85or
86.Ar half-duplex
87modes.
88.It 100baseTX
89Set 100Mbps (Fast Ethernet) operation.
90The
91.Ar mediaopt
92option can also be used to select either
93.Ar full-duplex
94or
95.Ar half-duplex
96modes.
97.El
98.Pp
99The
100.Nm
101driver supports the following media options:
102.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
103.It full-duplex
104Force full duplex operation.
105.It half-duplex
106Force half duplex operation.
107.El
108.Pp
109For more information on configuring this device, see
110.Xr ifconfig 8 .
111.Sh HARDWARE
112The
113.Nm
114driver supports Sundance Technologies ST201 based Fast Ethernet
115adapters and embedded controllers including:
116.Pp
117.Bl -bullet -compact
118.It
119D-Link DFE-530TXS
120.It
121D-Link DFE-550TX
122.It
123D-Link DFE-580TX
124.El
125.Sh SYSCTL VARIABLES
126The following variables are available as both
127.Xr sysctl 8
128variables and
129.Xr loader 8
130tunables:
131.Bl -tag -width "xxxxxx"
132.It Va dev.ste.%d.int_rx_mod
133Maximum number of time to delay RX interrupts.
134The valid range is 0 to 209712 in units of 1us, the default is
135150 (150us).
136The value 0 effectively disables the RX interrupt moderation.
137The resolution of timer is about 3.2us so finer tuning than
1383.2us wouldn't be available.
139The interface does not need to be brought down and up again before
140a change takes effect.
141.El
142.Sh DIAGNOSTICS
143.Bl -diag
144.It "ste%d: couldn't map ports/memory"
145A fatal initialization error has occurred.
146.It "ste%d: couldn't map interrupt"
147A fatal initialization error has occurred.
148.It "ste%d: watchdog timeout"
149The device has stopped responding to the network, or there is a problem with
150the network connection (cable).
151.It "ste%d: no memory for rx list"
152The driver failed to allocate an mbuf for the receiver ring.
153.It "ste%d: no memory for tx list"
154The driver failed to allocate an mbuf for the transmitter ring when
155allocating a pad buffer or collapsing an mbuf chain into a cluster.
156.It "ste%d: chip is in D3 power state -- setting to D0"
157This message applies only to adapters which support power
158management.
159Some operating systems place the controller in low power
160mode when shutting down, and some PCI BIOSes fail to bring the chip
161out of this state before configuring it.
162The controller loses all of
163its PCI configuration in the D3 state, so if the BIOS does not set
164it back to full power mode in time, it will not be able to configure it
165correctly.
166The driver tries to detect this condition and bring
167the adapter back to the D0 (full power) state, but this may not be
168enough to return the driver to a fully operational condition.
169If
170you see this message at boot time and the driver fails to attach
171the device as a network interface, you will have to perform a second
172warm boot to have the device properly configured.
173.Pp
174Note that this condition only occurs when warm booting from another
175operating system.
176If you power down your system prior to booting
177.Fx ,
178the card should be configured correctly.
179.El
180.Sh SEE ALSO
181.Xr altq 4 ,
182.Xr arp 4 ,
183.Xr miibus 4 ,
184.Xr netintro 4 ,
185.Xr ng_ether 4 ,
186.Xr polling 4 ,
187.Xr vlan 4 ,
188.Xr ifconfig 8
189.Rs
190.%T Sundance ST201 data sheet
191.Re
192.Sh HISTORY
193The
194.Nm
195device driver first appeared in
196.Fx 3.0 .
197.Sh AUTHORS
198The
199.Nm
200driver was written by
201.An Bill Paul Aq Mt wpaul@ee.columbia.edu .
202