Kconfig 16 KB

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