1 .\" Copyright (c) 1997, 1998, 1999
2 .\" Bill Paul <wpaul@ee.columbia.edu>. All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, are permitted provided that the following conditions
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.
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.
31 .\" $FreeBSD: src/share/man/man4/sis.4,v 1.6.2.4 2003/02/17 21:20:39 trhodes Exp $
32 .\" $DragonFly: src/share/man/man4/sis.4,v 1.5 2007/02/25 12:03:07 swildner Exp $
39 .Nd "SiS 900, SiS 7016 and NS DP83815 fast ethernet device driver"
46 driver provides support for PCI ethernet adapters and embedded
47 controllers based on the Silicon Integrated Systems SiS 900
48 and SiS 7016 fast ethernet controller chips, as well as support
49 for adapters based on the National Semiconductor DP83815 (MacPhyter)
50 PCI ethernet controller chip, including the Netgear FA311-TX and
53 The SiS 900 is a 100Mbps ethernet MAC and MII-compliant transceiver
55 It uses a bus master DMA and a scatter/gather
57 The SiS 7016 is similar to the SiS 900 except
58 that it has no internal PHY, requiring instead an external transceiver
59 to be attached to its MII interface.
60 The SiS 900 and SiS 7016 both have a 128-bit multicast hash filter
61 and a single perfect filter entry for the station address.
63 The NS DP83815 is also a 100Mbps ethernet MAC with integrated PHY.
64 The NatSemi chip and the SiS 900 share many of the same features and
65 a fairly similar programming interface, hence both chips are supported
70 driver supports the following media types:
72 .Bl -tag -width 10baseTXUTP
74 Enable autoselection of the media type and options.
75 The user can manually override
76 the autoselected mode by adding media options to
83 option can also be used to select either
89 Set 100Mbps (fast ethernet) operation.
93 option can also be used to select either
102 driver supports the following media options:
104 .Bl -tag -width full-duplex
106 Force full duplex operation
108 Force half duplex operation.
111 For more information on configuring this device, see
115 .It "sis%d: couldn't map ports/memory"
116 A fatal initialization error has occurred.
117 .It "sis%d: couldn't map interrupt"
118 A fatal initialization error has occurred.
119 .It "sis%d: watchdog timeout"
120 The device has stopped responding to the network, or there is a problem with
121 the network connection (e.g. a cable fault).
122 .It "sis%d: no memory for rx list"
123 The driver failed to allocate an mbuf for the receiver ring.
124 .It "sis%d: no memory for tx list"
125 The driver failed to allocate an mbuf for the transmitter ring when
126 allocating a pad buffer or collapsing an mbuf chain into a clusisr.
127 .It "sis%d: chip is in D3 power state -- setting to D0"
128 This message applies only to adapters which support power
130 Some operating systems place the controller in low power
131 mode when shutting down, and some PCI BIOSes fail to bring the chip
132 out of this state before configuring it.
133 The controller loses all of
134 its PCI configuration in the D3 state, so if the BIOS does not set
135 it back to full power mode in time, it will not be able to configure it
137 The driver tries to detect this condition and bring
138 the adapter back to the D0 (full power) state, but this may not be
139 enough to return the driver to a fully operational condition.
141 you see this message at boot time and the driver fails to attach
142 the device as a network interface, you will have to perform a
143 warm boot to have the device properly configured.
145 Note that this condition only occurs when warm booting from another
147 If you power down your system prior to booting
149 the card should be configured correctly.
160 .%T SiS 900 and SiS 7016 datasheets
161 .%O http://www.sis.com.tw
164 .%T NatSemi DP83815 datasheet
165 .%O http://www.national.com
170 device driver first appeared in
175 driver was written by
176 .An Bill Paul Aq wpaul@ee.columbia.edu .