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