summaryrefslogtreecommitdiff
path: root/share/man/man4/fxp.4
blob: 17e742d5ed230f16a6da883093af5e3acdf2c2e2 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
.\"	$OpenBSD: fxp.4,v 1.31 2004/12/22 14:44:41 jmc Exp $
.\"
.\" Copyright (c) 1997 David E. O'Brien
.\"
.\" All rights reserved.
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\"    notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\"    notice, this list of conditions and the following disclaimer in the
.\"    documentation and/or other materials provided with the distribution.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE DEVELOPERS ``AS IS'' AND ANY EXPRESS OR
.\" IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
.\" OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED.
.\" IN NO EVENT SHALL THE DEVELOPERS BE LIABLE FOR ANY DIRECT, INDIRECT,
.\" INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT
.\" NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,
.\" DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY
.\" THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
.\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
.\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
.\"
.Dd April 28, 1998
.Dt FXP 4
.Os
.Sh NAME
.Nm fxp
.Nd Intel EtherExpress PRO/100 Ethernet driver
.Sh SYNOPSIS
.Cd "fxp* at pci?"
.Cd "fxp* at cardbus?"
.Cd "icsphy* at mii?"
.Cd "inphy* at mii?"
.Cd "nsphy* at mii?"
.Sh DESCRIPTION
The
.Nm
device driver supports the Intel EtherExpress 100 family of Ethernet cards
based on various revisions of the i82557, i82558, i82559,
i82550, i82551, and i82562 chipsets.
These come in several different varieties, including dual-port cards, and
as built-in Ethernet solutions on certain motherboards.
This includes, among others, the following models:
.Pp
.Bl -item -offset indent -compact
.It
Intel EtherExpress PRO/100 PCI
.It
Intel EtherExpress PRO/100B PCI
.It
Intel EtherExpress PRO/100+ PCI
.It
Intel EtherExpress PRO/100 Dual-Port PCI
.It
Intel PRO/100 CardBus II PC Card
.It
Intel PRO/100 VE
.It
Intel PRO/100 VM
.It
Intel PRO/100 M
.El
.Pp
Other models of Intel network cards are supported by the
.Xr ie 4 ,
.Xr iy 4 ,
and
.Xr em 4
drivers.
This list is not exhaustive.
In particular, the
.Nm
driver should support any card by any manufacturer which is based on one of the
aforementioned chipsets.
.Pp
The following media types and options (as given to
.Xr ifconfig 8 )
are supported:
.Bl -tag -width xxx -offset indent
.It Cm media No autoselect
Enable autoselection of the media type and options (default).
.It Cm media No 100baseTX Cm mediaopt No full-duplex
Set 100Mbps (Fast Ethernet) operation and force full-duplex mode.
.It Cm media No 100baseTX Cm mediaopt No half-duplex
Set 100Mbps (Fast Ethernet) operation and force half-duplex mode.
.It Cm media No 10baseT Cm mediaopt No full-duplex
Set 10Mbps operation and force full-duplex.
.It Cm media No 10baseT Cm mediaopt No half-duplex
Set 10Mbps operation and force half-duplex.
.El
.Pp
If no media options are present, the
.Nm
driver places the card into autoselect mode.
.Pp
These cards also come with a variety of PHYs.
Models exist with PHYs supported by both the
.Xr inphy 4
and
.Xr nsphy 4
drivers.
.Sh FILES
Some devices are able to do interrupt coalescing but it requires firmware
updating.
The following firmware files are potentially loaded on demand when an
interface is brought up:
.Pp
.Bl -tag -width Ds -offset indent -compact
.It Pa /etc/firmware/fxp-d101a
.It Pa /etc/firmware/fxp-d101b0
.It Pa /etc/firmware/fxp-d101ma
.It Pa /etc/firmware/fxp-d101s
.It Pa /etc/firmware/fxp-d102
.It Pa /etc/firmware/fxp-d102c
.It Pa /etc/firmware/fxp-license
.El
.Pp
If a file is missing, the driver attempts to operate anyway.
.Sh DIAGNOSTICS
.Bl -diag
.It "fxp%d: couldn't map memory"
A fatal initialization error has occurred.
.It "fxp%d: couldn't map interrupt"
A fatal initialization error has occurred.
.It "fxp%d: Failed to malloc memory"
There are not enough mbufs available for allocation.
.It "fxp%d: device timeout"
The device has stopped responding to the network, or there is a problem with
the network connection (cable).
.It "fxp%d: failed loadfirmware of file %s: errno %d"
The device is able to do interrupt coalescing but required firmware file
is missing.
.El
.Sh SEE ALSO
.Xr arp 4 ,
.Xr cardbus 4 ,
.Xr em 4 ,
.Xr icsphy 4 ,
.Xr ie 4 ,
.Xr ifmedia 4 ,
.Xr inphy 4 ,
.Xr intro 4 ,
.Xr iophy 4 ,
.Xr iy 4 ,
.Xr netintro 4 ,
.Xr nsphy 4 ,
.Xr pci 4 ,
.Xr hostname.if 5 ,
.Xr ifconfig 8
.Sh HISTORY
The
.Nm
device driver first appeared in
.Ox 2.2 .
.Sh AUTHORS
The
.Nm
device driver was written by David Greenman.
This manual page was written by David E. O'Brien.