[deliverable/linux.git] / drivers / atm / Kconfig

#
# ATM device configuration
#

menu "ATM drivers"
	depends on NETDEVICES && ATM

config ATM_DUMMY
	tristate "Dummy ATM driver"
	depends on ATM
	help
	  Dummy ATM driver. Useful for proxy signalling, testing,
	  and development.  If unsure, say N.

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.

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