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