1 .\" All Rights Reserved, Copyright (C) Fujitsu Limited 1995
3 .\" This document may be used, modified, copied, distributed, and sold, in
4 .\" both source and printed form provided that the above copyright, these
5 .\" terms and the following disclaimer are retained. The name of the author
6 .\" and/or the contributor may not be used to endorse or promote products
7 .\" derived from this software without specific prior written permission.
9 .\" THIS DOCUMENT IS PROVIDED BY THE AUTHOR AND THE CONTRIBUTOR ``AS IS'' AND
10 .\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
11 .\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
12 .\" ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR THE CONTRIBUTOR BE LIABLE
13 .\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
14 .\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
15 .\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
16 .\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
17 .\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
18 .\" OUT OF THE USE OF THIS DOCUMENT, EVEN IF ADVISED OF THE POSSIBILITY OF
21 .\" Contributed by M. Sekiguchi <seki@sysrap.cs.fujitsu.co.jp>.
30 .Nd "Fujitsu MB86960A/MB86965A based Ethernet adapters"
32 To compile this driver into the kernel,
33 place the following line in your
34 kernel configuration file:
35 .Bd -ragged -offset indent
39 Alternatively, to load the driver as a
40 module at boot time, place the following line in
42 .Bd -literal -offset indent
47 .Pa /boot/device.hints :
48 .Cd hint.fe.0.at="isa"
49 .Cd hint.fe.0.port="0x300"
50 .Cd hint.fe.0.flags="0x0"
51 .Sh DEPRECATION NOTICE
54 driver is not present in
57 See https://github.com/freebsd/fcp/blob/master/fcp-0101.md for more
62 is a network device driver
63 for Ethernet adapters based on Fujitsu MB86960A, MB86965A,
64 or other compatible chips.
66 The driver provides automatic I/O port address configuration and
67 automatic IRQ configuration,
68 when used with suitable adapter hardware.
70 The driver works with program I/O data transfer technique.
71 It gives a fair performance.
72 Shared memory is never used, even if the adapter has one.
74 It currently works with Fujitsu FMV-180 series for ISA,
75 Allied-Telesis AT1700 series and RE2000 series for ISA,
76 and Fujitsu MBH10302 PC card.
79 .Pa /boot/device.hints
84 must be specified to reflect adapter hardware settings.
87 can be specified to provide additional configuration as an option.
91 parameter specifies a base I/O port address of the adapter.
92 It must match with the hardware setting of the adapter.
95 may be left unspecified by removing
96 .Dl hint.fe.0.port="..."
98 In that case, the driver tries to detect the hardware setting
99 of the I/O address automatically.
100 This feature may not work with some adapter hardware.
104 parameter specifies an IRQ number used by the adapter.
105 It must match the hardware setting of the adapter.
107 may be left unspecified by removing
108 .Dl hint.fe.0.irq="..."
110 in that case, the driver tries to detect
111 the hardware setting of the IRQ automatically.
112 This feature may not work on some adapters.
116 is a numeric value which consists of a combination of various device settings.
117 The following flags are defined in the current version.
118 To specify two or more settings for a device,
119 use a numeric sum of each flag value.
120 Flag bits not specified below are reserved and must be set to 0.
121 Actually, each bit is either just ignored by the driver,
122 or tested and used to control undocumented features of the driver.
123 Consult the source program for undocumented features.
126 These flag bits are used
127 to initialize DLCR6 register of MB86960A/MB86965A chip,
133 See below for more about DLCR6 override feature.
136 flag bits must be 0 unless the
139 to maintain the compatibility with future versions of the driver.
141 This flag overrides the default setting to the DLCR6 register
142 of MB86960A/MB86965A chip by a user supplied value,
143 which is taken from the lower 7 bits of the flag value.
144 This is a troubleshooting flag and should not be used
145 without understanding of the adapter hardware.
146 Consult the Fujitsu manual for more information
150 Controllers and cards supported by the
156 Allied Telesis RE1000, RE1000Plus, ME1500 (110-pin)
158 CONTEC C-NET(98)P2, C-NET (9N)E (110-pin), C-NET(9N)C (ExtCard)
160 CONTEC C-NET(PC)C PC Card Ethernet
166 Fujitsu FMV-J182, FMV-J182A
168 Fujitsu MB86960A, MB86965A
170 Fujitsu MBH10303, MBH10302 PC Card Ethernet
172 Fujitsu Towa LA501 Ethernet
174 HITACHI HT-4840-11 PC Card Ethernet
176 NextCom J Link NC5310
178 RATOC REX-5588, REX-9822, REX-4886, and REX-R280
180 RATOC REX-9880/9881/9882/9883
182 TDK LAC-98012, LAC-98013, LAC-98025, LAC-9N011 (110-pin)
184 TDK LAK-CD011, LAK-CD021, LAK-CD021A, LAK-CD021BX
186 Ungermann-Bass Access/PC N98C+(PC85152, PC85142), Access/NOTE
187 N98(PC86132) (110-pin)
189 .Sh FEATURES SPECIFIC TO HARDWARE MODELS
192 driver has some features and limitations
193 which depend on adapter hardware models.
194 The following is a summary of these dependencies.
195 .Ss Fujitsu FMV-180 series adapters
196 Both automatic IRQ detection and automatic I/O port address detection
197 is available with these adapters.
199 Automatic I/O port address detection feature of
201 works mostly fine for FMV-180 series.
202 It works even if there are two or more FMV-180s in a system.
203 However, some combination of other adapters may confuse the driver.
204 It is recommended to explicitly specify
206 when you experience some difficulties with hardware probe.
208 Automatic IRQ detection feature of
210 works reliably for FMV-180 series.
211 It is recommended to explicitly specify
214 The hardware setting of IRQ is read
215 from the configuration EEPROM on the adapter,
216 even when the kernel config file specifies an IRQ value.
217 The driver will generate a warning message,
218 if the IRQ setting specified in
219 .Pa /boot/device.hints
220 does not match one stored in EEPROM.
221 Then, it will use the value specified in the file.
222 (This behavior has been changed from the previous releases.)
223 .Ss Allied-Telesis AT1700 series and RE2000 series adapters
224 Automatic I/O port address detection
225 is available with Allied-Telesis AT1700 series and RE2000 series,
226 while it is less reliable than FMV-180 series.
227 Using the feature with Allied-Telesis adapters
230 Automatic IRQ detection is also available with some limitation.
234 tries to get IRQ setting from the configuration EEPROM on the board,
238 .Pa /boot/device.hints .
240 AT1700 series and RE2000 series seems to have two types of models;
241 One type allows IRQ selection from 3/4/5/9,
242 while the other from 10/11/12/15.
243 Identification of the models are not well known.
244 Hence, automatic IRQ detection with Allied-Telesis adapters
246 Specify an exact IRQ number if any troubles are encountered.
248 Differences between AT1700 series and RE2000 series
249 or minor models in those series are not recognized.
250 .Ss Fujitsu MBH10302 PC card
253 driver supports Fujitsu MBH10302 and compatible PC cards.
254 It requires the PC card (PCMCIA) support package.
266 .Sh AUTHORS, COPYRIGHT AND DISCLAIMER
269 driver was originally written and contributed by
270 .An M. Sekiguchi Aq Mt seki@sysrap.cs.fujitsu.co.jp ,
278 .An Hidetoshi Kimura Aq Mt h-kimura@tokyo.se.fujitsu.co.jp .
279 This manual page was written by
282 .Em "All Rights Reserved, Copyright (C) Fujitsu Limited 1995"
284 This document and the associated software may be used, modified,
285 copied, distributed, and sold, in both source and binary form provided
286 that the above copyright, these terms and the following disclaimer are
288 The name of the author and/or the contributor may not be
289 used to endorse or promote products derived from this document and the
290 associated software without specific prior written permission.
292 THIS DOCUMENT AND THE ASSOCIATED SOFTWARE IS PROVIDED BY THE AUTHOR
295 AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
296 THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
297 PURPOSE ARE DISCLAIMED.
298 IN NO EVENT SHALL THE AUTHOR OR THE
299 CONTRIBUTOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
300 EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
301 PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
302 PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
303 LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
304 NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
305 DOCUMENT AND THE ASSOCIATED SOFTWARE, EVEN IF ADVISED OF THE
306 POSSIBILITY OF SUCH DAMAGE.
308 Following are major known bugs:
310 Statistics on the number of collisions maintained by the
312 driver is not accurate;
317 shows slightly less value than true number of collisions.
319 More mbuf clusters are used than expected.
320 The packet receive routine has an intended violation
321 against the mbuf cluster allocation policy.
322 The unnecessarily allocated clusters are freed within short lifetime,
323 and it will not affect long term kernel memory usage.
325 Although XNS and IPX support is included in the driver,
326 it has never been tested and it is expected to have a lot of bugs.