1.\" $OpenBSD: ste.4,v 1.8 2001/06/23 07:03:59 pjanzen Exp $ 2.\" 3.\" Copyright (c) 1997, 1998, 1999 4.\" Bill Paul <wpaul@ctr.columbia.edu>. All rights reserved. 5.\" 6.\" Redistribution and use in source and binary forms, with or without 7.\" modification, are permitted provided that the following conditions 8.\" are met: 9.\" 1. Redistributions of source code must retain the above copyright 10.\" notice, this list of conditions and the following disclaimer. 11.\" 2. Redistributions in binary form must reproduce the above copyright 12.\" notice, this list of conditions and the following disclaimer in the 13.\" documentation and/or other materials provided with the distribution. 14.\" 3. All advertising materials mentioning features or use of this software 15.\" must display the following acknowledgement: 16.\" This product includes software developed by Bill Paul. 17.\" 4. Neither the name of the author nor the names of any co-contributors 18.\" may be used to endorse or promote products derived from this software 19.\" without specific prior written permission. 20.\" 21.\" THIS SOFTWARE IS PROVIDED BY Bill Paul AND CONTRIBUTORS ``AS IS'' AND 22.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE 23.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE 24.\" ARE DISCLAIMED. IN NO EVENT SHALL Bill Paul OR THE VOICES IN HIS HEAD 25.\" BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR 26.\" CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF 27.\" SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS 28.\" INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN 29.\" CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) 30.\" ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF 31.\" THE POSSIBILITY OF SUCH DAMAGE. 32.\" 33.\" $FreeBSD: src/share/man/man4/ste.4,v 1.3 1999/11/15 23:14:27 phantom Exp $ 34.\" 35.Dd August 21, 1999 36.Dt STE 4 37.Os 38.Sh NAME 39.Nm ste 40.Nd Sundance Technologies ST201 Fast Ethernet driver 41.Sh SYNOPSIS 42.Cd "ste* at pci? dev ? function ?" 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. This includes the D-Link DFE-550TX. 49.Pp 50The Sundance ST201 uses bus master DMA and is designed to be a 513Com Etherlink XL work-alike. It uses the same DMA descriptor 52structure and is very similar in operation, however its register 53layout is different. The ST201 has a 64-bit multicast hash filter 54and a single perfect filter entry for the station address. IT 55supports both 10 and 100Mbps speeds in either full or half duplex 56using an MII transceiver. 57.Pp 58The 59.Nm 60driver supports the following media types: 61.Pp 62.Bl -tag -width xxxxxxxxxxxxxxxxxxxx 63.It autoselect 64Enable autoselection of the media type and options. 65The user can manually override 66the autoselected mode by adding media options to the 67.Xr hostname.if 5 68file. 69.It 10baseT/UTP 70Set 10Mbps operation. The 71.Ar mediaopt 72option can also be used to select either 73.Ar full-duplex 74or 75.Ar half-duplex 76modes. 77.It 100baseTX 78Set 100Mbps (Fast Ethernet) operation. The 79.Ar mediaopt 80option can also be used to select either 81.Ar full-duplex 82or 83.Ar half-duplex 84modes. 85.El 86.Pp 87The 88.Nm 89driver supports the following media options: 90.Pp 91.Bl -tag -width xxxxxxxxxxxxxxxxxxxx 92.It full-duplex 93Force full duplex operation 94.It half-duplex 95Force half duplex operation. 96.El 97.Pp 98For more information on configuring this device, see 99.Xr ifconfig 8 . 100.Sh DIAGNOSTICS 101.Bl -diag 102.It "ste%d: couldn't map ports/memory" 103A fatal initialization error has occurred. 104.It "ste%d: couldn't map interrupt" 105A fatal initialization error has occurred. 106.It "ste%d: watchdog timeout" 107The device has stopped responding to the network, or there is a problem with 108the network connection (cable). 109.It "ste%d: no memory for rx list" 110The driver failed to allocate an mbuf for the receiver ring. 111.It "ste%d: no memory for tx list" 112The driver failed to allocate an mbuf for the transmitter ring when 113allocating a pad buffer or collapsing an mbuf chain into a cluster. 114.It "ste%d: chip is in D3 power state -- setting to D0" 115This message applies only to adapters which support power 116management. Some operating systems place the controller in low power 117mode when shutting down, and some PCI BIOSes fail to bring the chip 118out of this state before configuring it. The controller loses all of 119its PCI configuration in the D3 state, so if the BIOS does not set 120it back to full power mode in time, it won't be able to configure it 121correctly. The driver tries to detect this condition and bring 122the adapter back to the D0 (full power) state, but this may not be 123enough to return the driver to a fully operational condition. If 124you see this message at boot time and the driver fails to attach 125the device as a network interface, you will have to perform second 126warm boot to have the device properly configured. 127.Pp 128Note that this condition only occurs when warm booting from another 129operating system. If you power down your system prior to booting 130.Ox , 131the card should be configured correctly. 132.El 133.Sh SEE ALSO 134.Xr arp 4 , 135.Xr netintro 4 , 136.Xr ifconfig 8 137.Rs 138.%T Sundance ST201 data sheet 139.%O http://www.sundanceti.com 140.Re 141.Sh HISTORY 142The 143.Nm 144device driver first appeared in 145.Fx 3.0 . 146.Ox 147support was added in 148.Ox 2.7 . 149.Sh AUTHORS 150The 151.Nm 152driver was written by Bill Paul <wpaul@ee.columbia.edu> and ported to 153.Ox 154by Aaron Campbell <aaron@openbsd.org>. 155