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