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