xref: /freebsd/share/man/man4/sk.4 (revision 7773002178c8dbc52b44e4d705f07706409af8e4)
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 3, 1999
34.Dt SK 4
35.Os
36.Sh NAME
37.Nm sk
38.Nd "SysKonnect SK-984x and SK-982x PCI gigabit ethernet adapter driver"
39.Sh SYNOPSIS
40.Cd "device miibus"
41.Cd "device sk"
42.Sh DESCRIPTION
43The
44.Nm
45driver provides support for the SysKonnect SK-984x and SK-982x series PCI
46gigabit ethernet adapters, including the following:
47.Pp
48.Bl -bullet -offset indent -compact
49.It
50SK-9521 SK-NET GE-T single port, 1000baseT adapter
51.It
52SK-9821 SK-NET GE-T single port, 1000baseT adapter
53.It
54SK-9822 SK-NET GE-T dual port, 1000baseT adapter
55.It
56SK-9841 SK-NET GE-LX single port, single mode fiber adapter
57.It
58SK-9842 SK-NET GE-LX dual port, single mode fiber adapter
59.It
60SK-9843 SK-NET GE-SX single port, multimode fiber adapter
61.It
62SK-9844 SK-NET GE-SX dual port, multimode fiber adapter
63.It
643COM 3C940 single port, 1000baseT adapter
65.El
66.Pp
67The SysKonnect adapters consist of two main components: the XaQti Corp.
68XMAC II gigabit MAC and the SysKonnect GEnesis controller ASIC.
69The
70XMAC provides the gigabit MAC and PHY support while the GEnesis
71provides an interface to the PCI bus, DMA support, packet buffering
72and arbitration.
73The GEnesis can control up to two XMACs simultaneously,
74allowing dual-port NIC configurations.
75.Pp
76The SK-982x 1000baseT adapters also include a Broadcom BCM5400 1000baseTX
77PHY which is used in place of the XMAC's internal PHY.
78The Broadcom PHY is connected to the XMAC via its GMII port.
79.Pp
80The
81.Nm
82driver configures dual port SysKonnect adapters such that each XMAC
83is treated as a separate logical network interface.
84Both ports can
85operate independently of each other and can be connected to separate
86networks.
87The SysKonnect driver software currently only uses the
88second port on dual port adapters for failover purposes: if the link
89on the primary port fails, the SysKonnect driver will automatically
90switch traffic onto the second port.
91.Pp
92Also supported is the Marvell Semiconductor 88E1000* gigabit PHY.
93.Pp
94The XaQti XMAC II supports full and half duplex operation with
95autonegotiation.
96The XMAC also supports unlimited frame sizes.
97Support for jumbo frames is provided via the interface MTU setting.
98Selecting an MTU larger than 1500 bytes with the
99.Xr ifconfig 8
100utility configures the adapter to receive and transmit jumbo frames.
101Using jumbo frames can greatly improve performance for certain tasks,
102such as file transfers and data streaming.
103.Pp
104The
105.Nm
106driver supports the following media types:
107.Pp
108.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
109.It autoselect
110Enable autoselection of the media type and options.
111The user can manually override
112the autoselected mode by adding media options to the
113.Pa /etc/rc.conf
114file.
115.It 1000baseTX
116Set 1000baseTX operation over twisted pair.
117This is only available
118for SK-982x series adapters with 1000baseT ports.
119Both
120.Ar full-duplex
121and
122.Ar half-duplex
123modes are supported.
124.It 1000baseSX
125Set 1000Mbps (gigabit ethernet) operation.
126Both
127.Ar full-duplex
128and
129.Ar half-duplex
130modes are supported.
131.El
132.Pp
133The
134.Nm
135driver supports the following media options:
136.Pp
137.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
138.It full-duplex
139Force full duplex operation
140.It half-duplex
141Force half duplex operation.
142.El
143.Pp
144The
145.Nm
146driver also supports one special link option for 1000baseTX cards:
147.Pp
148.Bl -tag -width xxxxxxxxxxxxxxxxxxxx
149.It link0
150With 1000baseTX cards, establishing a link between two ports requires
151that one port be configured as a master and the other a slave.
152With autonegotiation,
153the master/slave settings will be chosen automatically.
154However when manually selecting the link state, it is necessary to
155force one side of the link to be a master and the other a slave.
156The
157.Nm
158driver configures the ports as slaves by default.
159Setting the
160.Ar link0
161flag with
162.Xr ifconfig 8
163will set a port as a master instead.
164.El
165.Pp
166For more information on configuring this device, see
167.Xr ifconfig 8 .
168.Sh DIAGNOSTICS
169.Bl -diag
170.It "sk%d: couldn't map memory"
171A fatal initialization error has occurred.
172.It "sk%d: couldn't map ports"
173A fatal initialization error has occurred.
174.It "sk%d: couldn't map interrupt"
175A fatal initialization error has occurred.
176.It "sk%d: no memory for softc struct!"
177The driver failed to allocate memory for per-device instance information
178during initialization.
179.It "sk%d: failed to enable memory mapping!"
180The driver failed to initialize PCI shared memory mapping.
181This might
182happen if the card is not in a bus-master slot.
183.It "sk%d: no memory for jumbo buffers!"
184The driver failed to allocate memory for jumbo frames during
185initialization.
186.It "sk%d: watchdog timeout"
187The device has stopped responding to the network, or there is a problem with
188the network connection (cable).
189.El
190.Sh SEE ALSO
191.Xr arp 4 ,
192.Xr netintro 4 ,
193.Xr ng_ether 4 ,
194.Xr vlan 4 ,
195.Xr ifconfig 8
196.Rs
197.%T XaQti XMAC II datasheet
198.%O http://www.xaqti.com
199.Re
200.Rs
201.%T SysKonnect GEnesis programming manual
202.%O http://www.syskonnect.com
203.Re
204.Sh HISTORY
205The
206.Nm
207device driver first appeared in
208.Fx 3.0 .
209.Sh AUTHORS
210The
211.Nm
212driver was written by
213.An Bill Paul Aq wpaul@ctr.columbia.edu .
214