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"
54 is a network device driver
55 for Ethernet adapters based on Fujitsu MB86960A, MB86965A,
56 or other compatible chips.
58 The driver provides automatic I/O port address configuration and
59 automatic IRQ configuration,
60 when used with suitable adapter hardware.
62 The driver works with program I/O data transfer technique.
63 It gives a fair performance.
64 Shared memory is never used, even if the adapter has one.
66 It currently works with Fujitsu FMV-180 series for ISA,
67 Allied-Telesis AT1700 series and RE2000 series for ISA,
68 and Fujitsu MBH10302 PC card.
71 .Pa /boot/device.hints
76 must be specified to reflect adapter hardware settings.
79 can be specified to provide additional configuration as an option.
83 parameter specifies a base I/O port address of the adapter.
84 It must match with the hardware setting of the adapter.
87 may be left unspecified by removing
88 .Dl hint.fe.0.port="..."
90 In that case, the driver tries to detect the hardware setting
91 of the I/O address automatically.
92 This feature may not work with some adapter hardware.
96 parameter specifies an IRQ number used by the adapter.
97 It must match the hardware setting of the adapter.
99 may be left unspecified by removing
100 .Dl hint.fe.0.irq="..."
102 in that case, the driver tries to detect
103 the hardware setting of the IRQ automatically.
104 This feature may not work on some adapters.
108 is a numeric value which consists of a combination of various device settings.
109 The following flags are defined in the current version.
110 To specify two or more settings for a device,
111 use a numeric sum of each flag value.
112 Flag bits not specified below are reserved and must be set to 0.
113 Actually, each bit is either just ignored by the driver,
114 or tested and used to control undocumented features of the driver.
115 Consult the source program for undocumented features.
118 These flag bits are used
119 to initialize DLCR6 register of MB86960A/MB86965A chip,
125 See below for more about DLCR6 override feature.
128 flag bits must be 0 unless the
131 to maintain the compatibility with future versions of the driver.
133 This flag overrides the default setting to the DLCR6 register
134 of MB86960A/MB86965A chip by a user supplied value,
135 which is taken from the lower 7 bits of the flag value.
136 This is a troubleshooting flag and should not be used
137 without understanding of the adapter hardware.
138 Consult the Fujitsu manual for more information
142 Controllers and cards supported by the
148 Allied Telesis RE1000, RE1000Plus, ME1500 (110-pin)
150 CONTEC C-NET(98)P2, C-NET (9N)E (110-pin), C-NET(9N)C (ExtCard)
152 CONTEC C-NET(PC)C PCMCIA Ethernet
158 Fujitsu FMV-J182, FMV-J182A
160 Fujitsu MB86960A, MB86965A
162 Fujitsu MBH10303, MBH10302 Ethernet PCMCIA
164 Fujitsu Towa LA501 Ethernet
168 NextCom J Link NC5310
170 RATOC REX-5588, REX-9822, REX-4886, and REX-R280
172 RATOC REX-9880/9881/9882/9883
174 TDK LAC-98012, LAC-98013, LAC-98025, LAC-9N011 (110-pin)
176 TDK LAK-CD021, LAK-CD021A, LAK-CD021BX
178 Ungermann-Bass Access/PC N98C+(PC85152, PC85142), Access/NOTE
179 N98(PC86132) (110-pin)
181 .Sh FEATURES SPECIFIC TO HARDWARE MODELS
184 driver has some features and limitations
185 which depend on adapter hardware models.
186 The following is a summary of these dependencies.
187 .Ss Fujitsu FMV-180 series adapters
188 Both automatic IRQ detection and automatic I/O port address detection
189 is available with these adapters.
191 Automatic I/O port address detection feature of
193 works mostly fine for FMV-180 series.
194 It works even if there are two or more FMV-180s in a system.
195 However, some combination of other adapters may confuse the driver.
196 It is recommended to explicitly specify
198 when you experience some difficulties with hardware probe.
200 Automatic IRQ detection feature of
202 works reliably for FMV-180 series.
203 It is recommended to explicitly specify
206 The hardware setting of IRQ is read
207 from the configuration EEPROM on the adapter,
208 even when the kernel config file specifies an IRQ value.
209 The driver will generate a warning message,
210 if the IRQ setting specified in
211 .Pa /boot/device.hints
212 does not match one stored in EEPROM.
213 Then, it will use the value specified in the file.
214 (This behavior has been changed from the previous releases.)
215 .Ss Allied-Telesis AT1700 series and RE2000 series adapters
216 Automatic I/O port address detection
217 is available with Allied-Telesis AT1700 series and RE2000 series,
218 while it is less reliable than FMV-180 series.
219 Using the feature with Allied-Telesis adapters
222 Automatic IRQ detection is also available with some limitation.
226 tries to get IRQ setting from the configuration EEPROM on the board,
230 .Pa /boot/device.hints .
232 AT1700 series and RE2000 series seems to have two types of models;
233 One type allows IRQ selection from 3/4/5/9,
234 while the other from 10/11/12/15.
235 Identification of the models are not well known.
236 Hence, automatic IRQ detection with Allied-Telesis adapters
238 Specify an exact IRQ number if any troubles are encountered.
240 Differences between AT1700 series and RE2000 series
241 or minor models in those series are not recognized.
242 .Ss Fujitsu MBH10302 PC card
245 driver supports Fujitsu MBH10302 and compatible PC cards.
246 It requires the PC card (PCMCIA) support package.
258 .Sh AUTHORS, COPYRIGHT AND DISCLAIMER
261 driver was originally written and contributed by
262 .An M. Sekiguchi Aq seki@sysrap.cs.fujitsu.co.jp ,
270 .An Hidetoshi Kimura Aq h-kimura@tokyo.se.fujitsu.co.jp .
271 This manual page was written by
274 .Em "All Rights Reserved, Copyright (C) Fujitsu Limited 1995"
276 This document and the associated software may be used, modified,
277 copied, distributed, and sold, in both source and binary form provided
278 that the above copyright, these terms and the following disclaimer are
280 The name of the author and/or the contributor may not be
281 used to endorse or promote products derived from this document and the
282 associated software without specific prior written permission.
284 THIS DOCUMENT AND THE ASSOCIATED SOFTWARE IS PROVIDED BY THE AUTHOR
287 AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO,
288 THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
289 PURPOSE ARE DISCLAIMED.
290 IN NO EVENT SHALL THE AUTHOR OR THE
291 CONTRIBUTOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,
292 EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,
293 PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
294 PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
295 LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING
296 NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS
297 DOCUMENT AND THE ASSOCIATED SOFTWARE, EVEN IF ADVISED OF THE
298 POSSIBILITY OF SUCH DAMAGE.
300 Following are major known bugs:
302 Statistics on the number of collisions maintained by the
304 driver is not accurate;
309 shows slightly less value than true number of collisions.
311 More mbuf clusters are used than expected.
312 The packet receive routine has an intended violation
313 against the mbuf cluster allocation policy.
314 The unnecessarily allocated clusters are freed within short lifetime,
315 and it will not affect long term kernel memory usage.
317 Although XNS and IPX support is included in the driver,
318 it has never been tested and it is expected to have a lot of bugs.