[linux-2.6] / drivers / atm / Kconfig

#
# ATM device configuration
#

menu "ATM drivers"
	depends on NETDEVICES && ATM

config ATM_TCP
	tristate "ATM over TCP"
	depends on INET && ATM
	help
	  ATM over TCP driver. Useful mainly for development and for
	  experiments. If unsure, say N.

config ATM_LANAI
	tristate "Efficient Networks Speedstream 3010"
	depends on PCI && ATM
	help
	  Supports ATM cards based on the Efficient Networks "Lanai"
	  chipset such as the Speedstream 3010 and the ENI-25p.  The
	  Speedstream 3060 is currently not supported since we don't
	  have the code to drive the on-board Alcatel DSL chipset (yet).

config ATM_ENI
	tristate "Efficient Networks ENI155P"
	depends on PCI && ATM
	---help---
	  Driver for the Efficient Networks ENI155p series and SMC ATM
	  Power155 155 Mbps ATM adapters. Both, the versions with 512KB and
	  2MB on-board RAM (Efficient calls them "C" and "S", respectively),
	  and the FPGA and the ASIC Tonga versions of the board are supported.
	  The driver works with MMF (-MF or ...F) and UTP-5 (-U5 or ...D)
	  adapters.

	  To compile this driver as a module, choose M here: the module will
	  be called eni.

config ATM_ENI_DEBUG
	bool "Enable extended debugging"
	depends on ATM_ENI
	help
	  Extended debugging records various events and displays that list
	  when an inconsistency is detected. This mechanism is faster than
	  generally using printks, but still has some impact on performance.
	  Note that extended debugging may create certain race conditions
	  itself. Enable this ONLY if you suspect problems with the driver.

config ATM_ENI_TUNE_BURST
	bool "Fine-tune burst settings"
	depends on ATM_ENI
	---help---
	  In order to obtain good throughput, the ENI NIC can transfer
	  multiple words of data per PCI bus access cycle. Such a multi-word
	  transfer is called a burst.

	  The default settings for the burst sizes are suitable for most PCI
	  chipsets. However, in some cases, large bursts may overrun buffers
	  in the PCI chipset and cause data corruption. In such cases, large
	  bursts must be disabled and only (slower) small bursts can be used.
	  The burst sizes can be set independently in the send (TX) and
	  receive (RX) direction.

	  Note that enabling many different burst sizes in the same direction
	  may increase the cost of setting up a transfer such that the
	  resulting throughput is lower than when using only the largest
	  available burst size.

	  Also, sometimes larger bursts lead to lower throughput, e.g. on an
	  Intel 440FX board, a drop from 135 Mbps to 103 Mbps was observed
	  when going from 8W to 16W bursts.

config ATM_ENI_BURST_TX_16W
	bool "Enable 16W TX bursts (discouraged)"
	depends on ATM_ENI_TUNE_BURST
	help
	  Burst sixteen words at once in the send direction. This may work
	  with recent PCI chipsets, but is known to fail with older chipsets.

config ATM_ENI_BURST_TX_8W
	bool "Enable 8W TX bursts (recommended)"
	depends on ATM_ENI_TUNE_BURST
	help
	  Burst eight words at once in the send direction. This is the default
	  setting.

config ATM_ENI_BURST_TX_4W
	bool "Enable 4W TX bursts (optional)"
	depends on ATM_ENI_TUNE_BURST
	help
	  Burst four words at once in the send direction. You may want to try
	  this if you have disabled 8W bursts. Enabling 4W if 8W is also set
	  may or may not improve throughput.

config ATM_ENI_BURST_TX_2W
	bool "Enable 2W TX bursts (optional)"
	depends on ATM_ENI_TUNE_BURST
	help
	  Burst two words at once in the send direction. You may want to try
	  this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or 8W
	  are also set may or may not improve throughput.

config ATM_ENI_BURST_RX_16W
	bool "Enable 16W RX bursts (discouraged)"
	depends on ATM_ENI_TUNE_BURST
	help
	  Burst sixteen words at once in the receive direction. This may work
	  with recent PCI chipsets, but is known to fail with older chipsets.

config ATM_ENI_BURST_RX_8W
	bool "Enable 8W RX bursts (discouraged)"
	depends on ATM_ENI_TUNE_BURST
	help
	  Burst eight words at once in the receive direction. This may work
	  with recent PCI chipsets, but is known to fail with older chipsets,
	  such as the Intel Neptune series.

config ATM_ENI_BURST_RX_4W
	bool "Enable 4W RX bursts (recommended)"
	depends on ATM_ENI_TUNE_BURST
	help
	  Burst four words at once in the receive direction. This is the
	  default setting. Enabling 4W if 8W is also set may or may not
	  improve throughput.

config ATM_ENI_BURST_RX_2W
	bool "Enable 2W RX bursts (optional)"
	depends on ATM_ENI_TUNE_BURST
	help
	  Burst two words at once in the receive direction. You may want to
	  try this if you have disabled 4W and 8W bursts. Enabling 2W if 4W or
	  8W are also set may or may not improve throughput.

config ATM_FIRESTREAM
	tristate "Fujitsu FireStream (FS50/FS155) "
	depends on PCI && ATM
	help
	  Driver for the Fujitsu FireStream 155 (MB86697) and
	  FireStream 50 (MB86695) ATM PCI chips.

	  To compile this driver as a module, choose M here: the module will
	  be called firestream.

config ATM_ZATM
	tristate "ZeitNet ZN1221/ZN1225"
	depends on PCI && ATM
	help
	  Driver for the ZeitNet ZN1221 (MMF) and ZN1225 (UTP-5) 155 Mbps ATM
	  adapters.

	  To compile this driver as a module, choose M here: the module will
	  be called zatm.

config ATM_ZATM_DEBUG
	bool "Enable extended debugging"
	depends on ATM_ZATM
	help
	  Extended debugging records various events and displays that list
	  when an inconsistency is detected. This mechanism is faster than
	  generally using printks, but still has some impact on performance.
	  Note that extended debugging may create certain race conditions
	  itself. Enable this ONLY if you suspect problems with the driver.

#   bool 'Rolfs TI TNETA1570' CONFIG_ATM_TNETA1570 y
#   if [ "$CONFIG_ATM_TNETA1570" = "y" ]; then
#      bool '  Enable extended debugging' CONFIG_ATM_TNETA1570_DEBUG n
#   fi
config ATM_NICSTAR
	tristate "IDT 77201 (NICStAR) (ForeRunnerLE)"
	depends on PCI && ATM && !64BIT
	help
	  The NICStAR chipset family is used in a large number of ATM NICs for
	  25 and for 155 Mbps, including IDT cards and the Fore ForeRunnerLE
	  series. Say Y if you have one of those.

	  To compile this driver as a module, choose M here: the module will
	  be called nicstar.

config ATM_NICSTAR_USE_SUNI
	bool "Use suni PHY driver (155Mbps)"
	depends on ATM_NICSTAR
	help
	  Support for the S-UNI and compatible PHYsical layer chips. These are
	  found in most 155Mbps NICStAR based ATM cards, namely in the
	  ForeRunner LE155 cards. This driver provides detection of cable~
	  removal and reinsertion and provides some statistics. This driver
	  doesn't have removal capability when compiled as a module, so if you
	  need that capability don't include S-UNI support (it's not needed to
	  make the card work).

config ATM_NICSTAR_USE_IDT77105
	bool "Use IDT77015 PHY driver (25Mbps)"
	depends on ATM_NICSTAR
	help
	  Support for the PHYsical layer chip in ForeRunner LE25 cards. In
	  addition to cable removal/reinsertion detection, this driver allows
	  you to control the loopback mode of the chip via a dedicated IOCTL.
	  This driver is required for proper handling of temporary carrier
	  loss, so if you have a 25Mbps NICStAR based ATM card you must say Y.

config ATM_IDT77252
	tristate "IDT 77252 (NICStAR II)"
	depends on PCI && ATM
	help
	  Driver for the IDT 77252 ATM PCI chips.

	  To compile this driver as a module, choose M here: the module will
	  be called idt77252.

config ATM_IDT77252_DEBUG
	bool "Enable debugging messages"
	depends on ATM_IDT77252
	help
	  Somewhat useful debugging messages are available. The choice of
	  messages is controlled by a bitmap.  This may be specified as a
	  module argument.  See the file <file:drivers/atm/idt77252.h> for
	  the meanings of the bits in the mask.

	  When active, these messages can have a significant impact on the
	  speed of the driver, and the size of your syslog files! When
	  inactive, they will have only a modest impact on performance.

config ATM_IDT77252_RCV_ALL
	bool "Receive ALL cells in raw queue"
	depends on ATM_IDT77252
	help
	  Enable receiving of all cells on the ATM link, that do not match
	  an open connection in the raw cell queue of the driver.  Useful
	  for debugging or special applications only, so the safe answer is N.

config ATM_IDT77252_USE_SUNI
	bool
	depends on ATM_IDT77252
	default y

config ATM_AMBASSADOR
	tristate "Madge Ambassador (Collage PCI 155 Server)"
	depends on PCI && ATM
	help
	  This is a driver for ATMizer based ATM card produced by Madge
	  Networks Ltd. Say Y (or M to compile as a module named ambassador)
	  here if you have one of these cards.

config ATM_AMBASSADOR_DEBUG
	bool "Enable debugging messages"
	depends on ATM_AMBASSADOR
	---help---
	  Somewhat useful debugging messages are available. The choice of
	  messages is controlled by a bitmap.  This may be specified as a
	  module argument (kernel command line argument as well?), changed
	  dynamically using an ioctl (not yet) or changed by sending the
	  string "Dxxxx" to VCI 1023 (where x is a hex digit).  See the file
	  <file:drivers/atm/ambassador.h> for the meanings of the bits in the
	  mask.

	  When active, these messages can have a significant impact on the
	  speed of the driver, and the size of your syslog files! When
	  inactive, they will have only a modest impact on performance.

config ATM_HORIZON
	tristate "Madge Horizon [Ultra] (Collage PCI 25 and Collage PCI 155 Client)"
	depends on PCI && ATM
	help
	  This is a driver for the Horizon chipset ATM adapter cards once
	  produced by Madge Networks Ltd. Say Y (or M to compile as a module
	  named horizon) here if you have one of these cards.

config ATM_HORIZON_DEBUG
	bool "Enable debugging messages"
	depends on ATM_HORIZON
	---help---
	  Somewhat useful debugging messages are available. The choice of
	  messages is controlled by a bitmap.  This may be specified as a
	  module argument (kernel command line argument as well?), changed
	  dynamically using an ioctl (not yet) or changed by sending the
	  string "Dxxxx" to VCI 1023 (where x is a hex digit).  See the file
	  <file:drivers/atm/horizon.h> for the meanings of the bits in the
	  mask.

	  When active, these messages can have a significant impact on the
	  speed of the driver, and the size of your syslog files! When
	  inactive, they will have only a modest impact on performance.

config ATM_IA
	tristate "Interphase ATM PCI x575/x525/x531"
	depends on PCI && ATM && !64BIT
	---help---
	  This is a driver for the Interphase (i)ChipSAR adapter cards
	  which include a variety of variants in term of the size of the
	  control memory (128K-1KVC, 512K-4KVC), the size of the packet
	  memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3,
	  UTP155, UTP25, DS3 and E3). Go to:
	  	<http://www.iphase.com/products/ClassSheet.cfm?ClassID=ATM>
	  for more info about the cards. Say Y (or M to compile as a module
	  named iphase) here if you have one of these cards.

	  See the file <file:Documentation/networking/iphase.txt> for further
	  details.

config ATM_IA_DEBUG
	bool "Enable debugging messages"
	depends on ATM_IA
	---help---
	  Somewhat useful debugging messages are available. The choice of
	  messages is controlled by a bitmap. This may be specified as a
	  module argument (kernel command line argument as well?), changed
	  dynamically using an ioctl (Get the debug utility, iadbg, from
	  <ftp://ftp.iphase.com/pub/atm/pci/>).

	  See the file <file:drivers/atm/iphase.h> for the meanings of the
	  bits in the mask.

	  When active, these messages can have a significant impact on the
	  speed of the driver, and the size of your syslog files! When
	  inactive, they will have only a modest impact on performance.

config ATM_FORE200E_MAYBE
	tristate "FORE Systems 200E-series"
	depends on (PCI || SBUS) && ATM
	---help---
	  This is a driver for the FORE Systems 200E-series ATM adapter
	  cards. It simultaneously supports PCA-200E and SBA-200E models
	  on PCI and SBUS hosts. Say Y (or M to compile as a module
	  named fore_200e) here if you have one of these ATM adapters.

	  Note that the driver will actually be compiled only if you
	  additionally enable the support for PCA-200E and/or SBA-200E
	  cards.

	  See the file <file:Documentation/networking/fore200e.txt> for
	  further details.

config ATM_FORE200E_PCA
	bool "PCA-200E support"
	depends on ATM_FORE200E_MAYBE && PCI
	help
	  Say Y here if you want your PCA-200E cards to be probed.

config ATM_FORE200E_PCA_DEFAULT_FW
	bool "Use default PCA-200E firmware (normally enabled)"
	depends on ATM_FORE200E_PCA
	help
	  Use the default PCA-200E firmware data shipped with the driver.

	  Normal users do not have to deal with the firmware stuff, so
	  they should say Y here.

config ATM_FORE200E_PCA_FW
	string "Pathname of user-supplied binary firmware"
	depends on ATM_FORE200E_PCA && !ATM_FORE200E_PCA_DEFAULT_FW
	default ""
	help
	  This defines the pathname of an alternative PCA-200E binary
	  firmware image supplied by the user. This pathname may be
	  absolute or relative to the drivers/atm directory.

	  The driver comes with an adequate firmware image, so normal users do
	  not have to supply an alternative one. They just say Y to "Use
	  default PCA-200E firmware" instead.

config ATM_FORE200E_SBA
	bool "SBA-200E support"
	depends on ATM_FORE200E_MAYBE && SBUS
	help
	  Say Y here if you want your SBA-200E cards to be probed.

config ATM_FORE200E_SBA_DEFAULT_FW
	bool "Use default SBA-200E firmware (normally enabled)"
	depends on ATM_FORE200E_SBA
	help
	  Use the default SBA-200E firmware data shipped with the driver.

	  Normal users do not have to deal with the firmware stuff, so
	  they should say Y here.

config ATM_FORE200E_SBA_FW
	string "Pathname of user-supplied binary firmware"
	depends on ATM_FORE200E_SBA && !ATM_FORE200E_SBA_DEFAULT_FW
	default ""
	help
	  This defines the pathname of an alternative SBA-200E binary
	  firmware image supplied by the user. This pathname may be
	  absolute or relative to the drivers/atm directory.

	  The driver comes with an adequate firmware image, so normal users do
	  not have to supply an alternative one. They just say Y to "Use
	  default SBA-200E firmware", above.

config ATM_FORE200E_USE_TASKLET
	bool "Defer interrupt work to a tasklet"
	depends on (PCI || SBUS) && (ATM_FORE200E_PCA || ATM_FORE200E_SBA)
	default n
	help
	  This defers work to be done by the interrupt handler to a
	  tasklet instead of hanlding everything at interrupt time.  This
	  may improve the responsive of the host.

config ATM_FORE200E_TX_RETRY
	int "Maximum number of tx retries"
	depends on (PCI || SBUS) && (ATM_FORE200E_PCA || ATM_FORE200E_SBA)
	default "16"
	---help---
	  Specifies the number of times the driver attempts to transmit
	  a message before giving up, if the transmit queue of the ATM card
	  is transiently saturated.

	  Saturation of the transmit queue may occur only under extreme
	  conditions, e.g. when a fast host continuously submits very small
	  frames (<64 bytes) or raw AAL0 cells (48 bytes) to the ATM adapter.

	  Note that under common conditions, it is unlikely that you encounter
	  a saturation of the transmit queue, so the retry mechanism never
	  comes into play.

config ATM_FORE200E_DEBUG
	int "Debugging level (0-3)"
	depends on (PCI || SBUS) && (ATM_FORE200E_PCA || ATM_FORE200E_SBA)
	default "0"
	help
	  Specifies the level of debugging messages issued by the driver.
	  The verbosity of the driver increases with the value of this
	  parameter.

	  When active, these messages can have a significant impact on
	  the performances of the driver, and the size of your syslog files!
	  Keep the debugging level to 0 during normal operations.

config ATM_FORE200E
	tristate
	depends on (PCI || SBUS) && (ATM_FORE200E_PCA || ATM_FORE200E_SBA)
	default m if ATM_FORE200E_MAYBE!=y
	default y if ATM_FORE200E_MAYBE=y

config ATM_HE
	tristate "ForeRunner HE Series"
	depends on PCI && ATM
	help
	  This is a driver for the Marconi ForeRunner HE-series ATM adapter
	  cards. It simultaneously supports the 155 and 622 versions.

config ATM_HE_USE_SUNI
	bool "Use S/UNI PHY driver"
	depends on ATM_HE
	help
	  Support for the S/UNI-Ultra and S/UNI-622 found in the ForeRunner
	  HE cards.  This driver provides carrier detection some statistics.

endmenu
Commit	Line	Data
1da177e4 LT	1	#
	2	# ATM device configuration
	3	#
	4
	5	menu "ATM drivers"
	6	depends on NETDEVICES && ATM
	7
	8	config 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
	15	config 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
	24	config 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
	38	config 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
	48	config 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
72	config 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
79	config 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
86	config 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
94	config 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
102	config 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
109	config 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
117	config 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
125	config 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
133	config 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
143	config 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
153	config 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
167	config 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
178	config 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
190	config 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
200	config 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
209	config 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
222	config 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
230	config ATM_IDT77252_USE_SUNI
231	bool
232	depends on ATM_IDT77252
233	default y
234
235	config 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
243	config 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
259	config 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
267	config 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
283	config 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
299	config 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
316	config 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
332	config 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
338	config 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
347	config 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
360	config 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
366	config 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
375	config 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
388	config 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
397	config 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
414	config 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
427	config 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
433	config 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
440	config 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
447	endmenu
448