Kconfig 16 KB

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