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