2 # ATM device configuration
6 depends on NETDEVICES && ATM
9 tristate "Dummy ATM driver"
12 Dummy ATM driver. Useful for proxy signalling, testing,
13 and development. If unsure, say N.
16 tristate "ATM over TCP"
17 depends on INET && ATM
19 ATM over TCP driver. Useful mainly for development and for
20 experiments. If unsure, say N.
23 tristate "Efficient Networks Speedstream 3010"
26 Supports ATM cards based on the Efficient Networks "Lanai"
27 chipset such as the Speedstream 3010 and the ENI-25p. The
28 Speedstream 3060 is currently not supported since we don't
29 have the code to drive the on-board Alcatel DSL chipset (yet).
32 tristate "Efficient Networks ENI155P"
35 Driver for the Efficient Networks ENI155p series and SMC ATM
36 Power155 155 Mbps ATM adapters. Both, the versions with 512KB and
37 2MB on-board RAM (Efficient calls them "C" and "S", respectively),
38 and the FPGA and the ASIC Tonga versions of the board are supported.
39 The driver works with MMF (-MF or ...F) and UTP-5 (-U5 or ...D)
42 To compile this driver as a module, choose M here: the module will
46 bool "Enable extended debugging"
49 Extended debugging records various events and displays that list
50 when an inconsistency is detected. This mechanism is faster than
51 generally using printks, but still has some impact on performance.
52 Note that extended debugging may create certain race conditions
53 itself. Enable this ONLY if you suspect problems with the driver.
55 config ATM_ENI_TUNE_BURST
56 bool "Fine-tune burst settings"
59 In order to obtain good throughput, the ENI NIC can transfer
60 multiple words of data per PCI bus access cycle. Such a multi-word
61 transfer is called a burst.
63 The default settings for the burst sizes are suitable for most PCI
64 chipsets. However, in some cases, large bursts may overrun buffers
65 in the PCI chipset and cause data corruption. In such cases, large
66 bursts must be disabled and only (slower) small bursts can be used.
67 The burst sizes can be set independently in the send (TX) and
68 receive (RX) direction.
70 Note that enabling many different burst sizes in the same direction
71 may increase the cost of setting up a transfer such that the
72 resulting throughput is lower than when using only the largest
75 Also, sometimes larger bursts lead to lower throughput, e.g. on an
76 Intel 440FX board, a drop from 135 Mbps to 103 Mbps was observed
77 when going from 8W to 16W bursts.
79 config ATM_ENI_BURST_TX_16W
80 bool "Enable 16W TX bursts (discouraged)"
81 depends on ATM_ENI_TUNE_BURST
83 Burst sixteen words at once in the send direction. This may work
84 with recent PCI chipsets, but is known to fail with older chipsets.
86 config ATM_ENI_BURST_TX_8W
87 bool "Enable 8W TX bursts (recommended)"
88 depends on ATM_ENI_TUNE_BURST
90 Burst eight words at once in the send direction. This is the default
93 config ATM_ENI_BURST_TX_4W
94 bool "Enable 4W TX bursts (optional)"
95 depends on ATM_ENI_TUNE_BURST
97 Burst four words at once in the send direction. You may want to try
98 this if you have disabled 8W bursts. Enabling 4W if 8W is also set
99 may or may not improve throughput.
101 config ATM_ENI_BURST_TX_2W
102 bool "Enable 2W TX bursts (optional)"
103 depends on ATM_ENI_TUNE_BURST
105 Burst two words at once in the send direction. You may want to try
106 this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or 8W
107 are also set may or may not improve throughput.
109 config ATM_ENI_BURST_RX_16W
110 bool "Enable 16W RX bursts (discouraged)"
111 depends on ATM_ENI_TUNE_BURST
113 Burst sixteen words at once in the receive direction. This may work
114 with recent PCI chipsets, but is known to fail with older chipsets.
116 config ATM_ENI_BURST_RX_8W
117 bool "Enable 8W RX bursts (discouraged)"
118 depends on ATM_ENI_TUNE_BURST
120 Burst eight words at once in the receive direction. This may work
121 with recent PCI chipsets, but is known to fail with older chipsets,
122 such as the Intel Neptune series.
124 config ATM_ENI_BURST_RX_4W
125 bool "Enable 4W RX bursts (recommended)"
126 depends on ATM_ENI_TUNE_BURST
128 Burst four words at once in the receive direction. This is the
129 default setting. Enabling 4W if 8W is also set may or may not
132 config ATM_ENI_BURST_RX_2W
133 bool "Enable 2W RX bursts (optional)"
134 depends on ATM_ENI_TUNE_BURST
136 Burst two words at once in the receive direction. You may want to
137 try this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or
138 8W are also set may or may not improve throughput.
140 config ATM_FIRESTREAM
141 tristate "Fujitsu FireStream (FS50/FS155) "
142 depends on PCI && ATM
144 Driver for the Fujitsu FireStream 155 (MB86697) and
145 FireStream 50 (MB86695) ATM PCI chips.
147 To compile this driver as a module, choose M here: the module will
148 be called firestream.
151 tristate "ZeitNet ZN1221/ZN1225"
152 depends on PCI && ATM
154 Driver for the ZeitNet ZN1221 (MMF) and ZN1225 (UTP-5) 155 Mbps ATM
157 To compile this driver as a module, choose M here: the module will
160 config ATM_ZATM_DEBUG
161 bool "Enable extended debugging"
164 Extended debugging records various events and displays that list
165 when an inconsistency is detected. This mechanism is faster than
166 generally using printks, but still has some impact on performance.
167 Note that extended debugging may create certain race conditions
168 itself. Enable this ONLY if you suspect problems with the driver.
170 # bool 'Rolfs TI TNETA1570' CONFIG_ATM_TNETA1570 y
171 # if [ "$CONFIG_ATM_TNETA1570" = "y" ]; then
172 # bool ' Enable extended debugging' CONFIG_ATM_TNETA1570_DEBUG n
175 tristate "IDT 77201 (NICStAR) (ForeRunnerLE)"
176 depends on PCI && ATM && !64BIT
178 The NICStAR chipset family is used in a large number of ATM NICs for
179 25 and for 155 Mbps, including IDT cards and the Fore ForeRunnerLE
180 series. Say Y if you have one of those.
182 To compile this driver as a module, choose M here: the module will
185 config ATM_NICSTAR_USE_SUNI
186 bool "Use suni PHY driver (155Mbps)"
187 depends on ATM_NICSTAR
189 Support for the S-UNI and compatible PHYsical layer chips. These are
190 found in most 155Mbps NICStAR based ATM cards, namely in the
191 ForeRunner LE155 cards. This driver provides detection of cable~
192 removal and reinsertion and provides some statistics. This driver
193 doesn't have removal capability when compiled as a module, so if you
194 need that capability don't include S-UNI support (it's not needed to
197 config ATM_NICSTAR_USE_IDT77105
198 bool "Use IDT77015 PHY driver (25Mbps)"
199 depends on ATM_NICSTAR
201 Support for the PHYsical layer chip in ForeRunner LE25 cards. In
202 addition to cable removal/reinsertion detection, this driver allows
203 you to control the loopback mode of the chip via a dedicated IOCTL.
204 This driver is required for proper handling of temporary carrier
205 loss, so if you have a 25Mbps NICStAR based ATM card you must say Y.
208 tristate "IDT 77252 (NICStAR II)"
209 depends on PCI && ATM
211 Driver for the IDT 77252 ATM PCI chips.
213 To compile this driver as a module, choose M here: the module will
216 config ATM_IDT77252_DEBUG
217 bool "Enable debugging messages"
218 depends on ATM_IDT77252
220 Somewhat useful debugging messages are available. The choice of
221 messages is controlled by a bitmap. This may be specified as a
222 module argument. See the file <file:drivers/atm/idt77252.h> for
223 the meanings of the bits in the mask.
225 When active, these messages can have a significant impact on the
226 speed of the driver, and the size of your syslog files! When
227 inactive, they will have only a modest impact on performance.
229 config ATM_IDT77252_RCV_ALL
230 bool "Receive ALL cells in raw queue"
231 depends on ATM_IDT77252
233 Enable receiving of all cells on the ATM link, that do not match
234 an open connection in the raw cell queue of the driver. Useful
235 for debugging or special applications only, so the safe answer is N.
237 config ATM_IDT77252_USE_SUNI
239 depends on ATM_IDT77252
242 config ATM_AMBASSADOR
243 tristate "Madge Ambassador (Collage PCI 155 Server)"
244 depends on PCI && ATM
247 This is a driver for ATMizer based ATM card produced by Madge
248 Networks Ltd. Say Y (or M to compile as a module named ambassador)
249 here if you have one of these cards.
251 config ATM_AMBASSADOR_DEBUG
252 bool "Enable debugging messages"
253 depends on ATM_AMBASSADOR
255 Somewhat useful debugging messages are available. The choice of
256 messages is controlled by a bitmap. This may be specified as a
257 module argument (kernel command line argument as well?), changed
258 dynamically using an ioctl (not yet) or changed by sending the
259 string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
260 <file:drivers/atm/ambassador.h> for the meanings of the bits in the
263 When active, these messages can have a significant impact on the
264 speed of the driver, and the size of your syslog files! When
265 inactive, they will have only a modest impact on performance.
268 tristate "Madge Horizon [Ultra] (Collage PCI 25 and Collage PCI 155 Client)"
269 depends on PCI && ATM
271 This is a driver for the Horizon chipset ATM adapter cards once
272 produced by Madge Networks Ltd. Say Y (or M to compile as a module
273 named horizon) here if you have one of these cards.
275 config ATM_HORIZON_DEBUG
276 bool "Enable debugging messages"
277 depends on ATM_HORIZON
279 Somewhat useful debugging messages are available. The choice of
280 messages is controlled by a bitmap. This may be specified as a
281 module argument (kernel command line argument as well?), changed
282 dynamically using an ioctl (not yet) or changed by sending the
283 string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
284 <file:drivers/atm/horizon.h> for the meanings of the bits in the
287 When active, these messages can have a significant impact on the
288 speed of the driver, and the size of your syslog files! When
289 inactive, they will have only a modest impact on performance.
292 tristate "Interphase ATM PCI x575/x525/x531"
293 depends on PCI && ATM && !64BIT
295 This is a driver for the Interphase (i)ChipSAR adapter cards
296 which include a variety of variants in term of the size of the
297 control memory (128K-1KVC, 512K-4KVC), the size of the packet
298 memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3,
299 UTP155, UTP25, DS3 and E3). Go to:
300 <http://www.iphase.com/products/ClassSheet.cfm?ClassID=ATM>
301 for more info about the cards. Say Y (or M to compile as a module
302 named iphase) here if you have one of these cards.
304 See the file <file:Documentation/networking/iphase.txt> for further
308 bool "Enable debugging messages"
311 Somewhat useful debugging messages are available. The choice of
312 messages is controlled by a bitmap. This may be specified as a
313 module argument (kernel command line argument as well?), changed
314 dynamically using an ioctl (Get the debug utility, iadbg, from
315 <ftp://ftp.iphase.com/pub/atm/pci/>).
317 See the file <file:drivers/atm/iphase.h> for the meanings of the
320 When active, these messages can have a significant impact on the
321 speed of the driver, and the size of your syslog files! When
322 inactive, they will have only a modest impact on performance.
324 config ATM_FORE200E_MAYBE
325 tristate "FORE Systems 200E-series"
326 depends on (PCI || SBUS) && ATM
328 This is a driver for the FORE Systems 200E-series ATM adapter
329 cards. It simultaneously supports PCA-200E and SBA-200E models
330 on PCI and SBUS hosts. Say Y (or M to compile as a module
331 named fore_200e) here if you have one of these ATM adapters.
333 Note that the driver will actually be compiled only if you
334 additionally enable the support for PCA-200E and/or SBA-200E
337 See the file <file:Documentation/networking/fore200e.txt> for
340 config ATM_FORE200E_PCA
341 bool "PCA-200E support"
342 depends on ATM_FORE200E_MAYBE && PCI
344 Say Y here if you want your PCA-200E cards to be probed.
346 config ATM_FORE200E_PCA_DEFAULT_FW
347 bool "Use default PCA-200E firmware (normally enabled)"
348 depends on ATM_FORE200E_PCA
350 Use the default PCA-200E firmware data shipped with the driver.
352 Normal users do not have to deal with the firmware stuff, so
353 they should say Y here.
355 config ATM_FORE200E_PCA_FW
356 string "Pathname of user-supplied binary firmware"
357 depends on ATM_FORE200E_PCA && !ATM_FORE200E_PCA_DEFAULT_FW
360 This defines the pathname of an alternative PCA-200E binary
361 firmware image supplied by the user. This pathname may be
362 absolute or relative to the drivers/atm directory.
364 The driver comes with an adequate firmware image, so normal users do
365 not have to supply an alternative one. They just say Y to "Use
366 default PCA-200E firmware" instead.
368 config ATM_FORE200E_SBA
369 bool "SBA-200E support"
370 depends on ATM_FORE200E_MAYBE && SBUS
372 Say Y here if you want your SBA-200E cards to be probed.
374 config ATM_FORE200E_SBA_DEFAULT_FW
375 bool "Use default SBA-200E firmware (normally enabled)"
376 depends on ATM_FORE200E_SBA
378 Use the default SBA-200E firmware data shipped with the driver.
380 Normal users do not have to deal with the firmware stuff, so
381 they should say Y here.
383 config ATM_FORE200E_SBA_FW
384 string "Pathname of user-supplied binary firmware"
385 depends on ATM_FORE200E_SBA && !ATM_FORE200E_SBA_DEFAULT_FW
388 This defines the pathname of an alternative SBA-200E binary
389 firmware image supplied by the user. This pathname may be
390 absolute or relative to the drivers/atm directory.
392 The driver comes with an adequate firmware image, so normal users do
393 not have to supply an alternative one. They just say Y to "Use
394 default SBA-200E firmware", above.
396 config ATM_FORE200E_USE_TASKLET
397 bool "Defer interrupt work to a tasklet"
398 depends on (PCI || SBUS) && (ATM_FORE200E_PCA || ATM_FORE200E_SBA)
401 This defers work to be done by the interrupt handler to a
402 tasklet instead of handling everything at interrupt time. This
403 may improve the responsive of the host.
405 config ATM_FORE200E_TX_RETRY
406 int "Maximum number of tx retries"
407 depends on (PCI || SBUS) && (ATM_FORE200E_PCA || ATM_FORE200E_SBA)
410 Specifies the number of times the driver attempts to transmit
411 a message before giving up, if the transmit queue of the ATM card
412 is transiently saturated.
414 Saturation of the transmit queue may occur only under extreme
415 conditions, e.g. when a fast host continuously submits very small
416 frames (<64 bytes) or raw AAL0 cells (48 bytes) to the ATM adapter.
418 Note that under common conditions, it is unlikely that you encounter
419 a saturation of the transmit queue, so the retry mechanism never
422 config ATM_FORE200E_DEBUG
423 int "Debugging level (0-3)"
424 depends on (PCI || SBUS) && (ATM_FORE200E_PCA || ATM_FORE200E_SBA)
427 Specifies the level of debugging messages issued by the driver.
428 The verbosity of the driver increases with the value of this
431 When active, these messages can have a significant impact on
432 the performances of the driver, and the size of your syslog files!
433 Keep the debugging level to 0 during normal operations.
437 depends on (PCI || SBUS) && (ATM_FORE200E_PCA || ATM_FORE200E_SBA)
438 default m if ATM_FORE200E_MAYBE!=y
439 default y if ATM_FORE200E_MAYBE=y
442 tristate "ForeRunner HE Series"
443 depends on PCI && ATM
445 This is a driver for the Marconi ForeRunner HE-series ATM adapter
446 cards. It simultaneously supports the 155 and 622 versions.
448 config ATM_HE_USE_SUNI
449 bool "Use S/UNI PHY driver"
452 Support for the S/UNI-Ultra and S/UNI-622 found in the ForeRunner
453 HE cards. This driver provides carrier detection some statistics.