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