Kconfig 16 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452
  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. config ATM_NICSTAR
  146. tristate "IDT 77201 (NICStAR) (ForeRunnerLE)"
  147. depends on PCI && ATM && !64BIT
  148. help
  149. The NICStAR chipset family is used in a large number of ATM NICs for
  150. 25 and for 155 Mbps, including IDT cards and the Fore ForeRunnerLE
  151. series. Say Y if you have one of those.
  152. To compile this driver as a module, choose M here: the module will
  153. be called nicstar.
  154. config ATM_NICSTAR_USE_SUNI
  155. bool "Use suni PHY driver (155Mbps)"
  156. depends on ATM_NICSTAR
  157. help
  158. Support for the S-UNI and compatible PHYsical layer chips. These are
  159. found in most 155Mbps NICStAR based ATM cards, namely in the
  160. ForeRunner LE155 cards. This driver provides detection of cable~
  161. removal and reinsertion and provides some statistics. This driver
  162. doesn't have removal capability when compiled as a module, so if you
  163. need that capability don't include S-UNI support (it's not needed to
  164. make the card work).
  165. config ATM_NICSTAR_USE_IDT77105
  166. bool "Use IDT77015 PHY driver (25Mbps)"
  167. depends on ATM_NICSTAR
  168. help
  169. Support for the PHYsical layer chip in ForeRunner LE25 cards. In
  170. addition to cable removal/reinsertion detection, this driver allows
  171. you to control the loopback mode of the chip via a dedicated IOCTL.
  172. This driver is required for proper handling of temporary carrier
  173. loss, so if you have a 25Mbps NICStAR based ATM card you must say Y.
  174. config ATM_IDT77252
  175. tristate "IDT 77252 (NICStAR II)"
  176. depends on PCI && ATM
  177. help
  178. Driver for the IDT 77252 ATM PCI chips.
  179. To compile this driver as a module, choose M here: the module will
  180. be called idt77252.
  181. config ATM_IDT77252_DEBUG
  182. bool "Enable debugging messages"
  183. depends on ATM_IDT77252
  184. help
  185. Somewhat useful debugging messages are available. The choice of
  186. messages is controlled by a bitmap. This may be specified as a
  187. module argument. See the file <file:drivers/atm/idt77252.h> for
  188. the meanings of the bits in the mask.
  189. When active, these messages can have a significant impact on the
  190. speed of the driver, and the size of your syslog files! When
  191. inactive, they will have only a modest impact on performance.
  192. config ATM_IDT77252_RCV_ALL
  193. bool "Receive ALL cells in raw queue"
  194. depends on ATM_IDT77252
  195. help
  196. Enable receiving of all cells on the ATM link, that do not match
  197. an open connection in the raw cell queue of the driver. Useful
  198. for debugging or special applications only, so the safe answer is N.
  199. config ATM_IDT77252_USE_SUNI
  200. bool
  201. depends on ATM_IDT77252
  202. default y
  203. config ATM_AMBASSADOR
  204. tristate "Madge Ambassador (Collage PCI 155 Server)"
  205. depends on PCI && ATM
  206. select BITREVERSE
  207. help
  208. This is a driver for ATMizer based ATM card produced by Madge
  209. Networks Ltd. Say Y (or M to compile as a module named ambassador)
  210. here if you have one of these cards.
  211. config ATM_AMBASSADOR_DEBUG
  212. bool "Enable debugging messages"
  213. depends on ATM_AMBASSADOR
  214. ---help---
  215. Somewhat useful debugging messages are available. The choice of
  216. messages is controlled by a bitmap. This may be specified as a
  217. module argument (kernel command line argument as well?), changed
  218. dynamically using an ioctl (not yet) or changed by sending the
  219. string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
  220. <file:drivers/atm/ambassador.h> for the meanings of the bits in the
  221. mask.
  222. When active, these messages can have a significant impact on the
  223. speed of the driver, and the size of your syslog files! When
  224. inactive, they will have only a modest impact on performance.
  225. config ATM_HORIZON
  226. tristate "Madge Horizon [Ultra] (Collage PCI 25 and Collage PCI 155 Client)"
  227. depends on PCI && ATM
  228. help
  229. This is a driver for the Horizon chipset ATM adapter cards once
  230. produced by Madge Networks Ltd. Say Y (or M to compile as a module
  231. named horizon) here if you have one of these cards.
  232. config ATM_HORIZON_DEBUG
  233. bool "Enable debugging messages"
  234. depends on ATM_HORIZON
  235. ---help---
  236. Somewhat useful debugging messages are available. The choice of
  237. messages is controlled by a bitmap. This may be specified as a
  238. module argument (kernel command line argument as well?), changed
  239. dynamically using an ioctl (not yet) or changed by sending the
  240. string "Dxxxx" to VCI 1023 (where x is a hex digit). See the file
  241. <file:drivers/atm/horizon.h> for the meanings of the bits in the
  242. mask.
  243. When active, these messages can have a significant impact on the
  244. speed of the driver, and the size of your syslog files! When
  245. inactive, they will have only a modest impact on performance.
  246. config ATM_IA
  247. tristate "Interphase ATM PCI x575/x525/x531"
  248. depends on PCI && ATM && !64BIT
  249. ---help---
  250. This is a driver for the Interphase (i)ChipSAR adapter cards
  251. which include a variety of variants in term of the size of the
  252. control memory (128K-1KVC, 512K-4KVC), the size of the packet
  253. memory (128K, 512K, 1M), and the PHY type (Single/Multi mode OC3,
  254. UTP155, UTP25, DS3 and E3). Go to:
  255. <http://www.iphase.com/products/ClassSheet.cfm?ClassID=ATM>
  256. for more info about the cards. Say Y (or M to compile as a module
  257. named iphase) here if you have one of these cards.
  258. See the file <file:Documentation/networking/iphase.txt> for further
  259. details.
  260. config ATM_IA_DEBUG
  261. bool "Enable debugging messages"
  262. depends on ATM_IA
  263. ---help---
  264. Somewhat useful debugging messages are available. The choice of
  265. messages is controlled by a bitmap. This may be specified as a
  266. module argument (kernel command line argument as well?), changed
  267. dynamically using an ioctl (Get the debug utility, iadbg, from
  268. <ftp://ftp.iphase.com/pub/atm/pci/>).
  269. See the file <file:drivers/atm/iphase.h> for the meanings of the
  270. bits in the mask.
  271. When active, these messages can have a significant impact on the
  272. speed of the driver, and the size of your syslog files! When
  273. inactive, they will have only a modest impact on performance.
  274. config ATM_FORE200E_MAYBE
  275. tristate "FORE Systems 200E-series"
  276. depends on (PCI || SBUS) && ATM
  277. ---help---
  278. This is a driver for the FORE Systems 200E-series ATM adapter
  279. cards. It simultaneously supports PCA-200E and SBA-200E models
  280. on PCI and SBUS hosts. Say Y (or M to compile as a module
  281. named fore_200e) here if you have one of these ATM adapters.
  282. Note that the driver will actually be compiled only if you
  283. additionally enable the support for PCA-200E and/or SBA-200E
  284. cards.
  285. See the file <file:Documentation/networking/fore200e.txt> for
  286. further details.
  287. config ATM_FORE200E_PCA
  288. bool "PCA-200E support"
  289. depends on ATM_FORE200E_MAYBE && PCI
  290. help
  291. Say Y here if you want your PCA-200E cards to be probed.
  292. config ATM_FORE200E_PCA_DEFAULT_FW
  293. bool "Use default PCA-200E firmware (normally enabled)"
  294. depends on ATM_FORE200E_PCA
  295. help
  296. Use the default PCA-200E firmware data shipped with the driver.
  297. Normal users do not have to deal with the firmware stuff, so
  298. they should say Y here.
  299. config ATM_FORE200E_PCA_FW
  300. string "Pathname of user-supplied binary firmware"
  301. depends on ATM_FORE200E_PCA && !ATM_FORE200E_PCA_DEFAULT_FW
  302. default ""
  303. help
  304. This defines the pathname of an alternative PCA-200E binary
  305. firmware image supplied by the user. This pathname may be
  306. absolute or relative to the drivers/atm directory.
  307. The driver comes with an adequate firmware image, so normal users do
  308. not have to supply an alternative one. They just say Y to "Use
  309. default PCA-200E firmware" instead.
  310. config ATM_FORE200E_SBA
  311. bool "SBA-200E support"
  312. depends on ATM_FORE200E_MAYBE && SBUS
  313. help
  314. Say Y here if you want your SBA-200E cards to be probed.
  315. config ATM_FORE200E_SBA_DEFAULT_FW
  316. bool "Use default SBA-200E firmware (normally enabled)"
  317. depends on ATM_FORE200E_SBA
  318. help
  319. Use the default SBA-200E firmware data shipped with the driver.
  320. Normal users do not have to deal with the firmware stuff, so
  321. they should say Y here.
  322. config ATM_FORE200E_SBA_FW
  323. string "Pathname of user-supplied binary firmware"
  324. depends on ATM_FORE200E_SBA && !ATM_FORE200E_SBA_DEFAULT_FW
  325. default ""
  326. help
  327. This defines the pathname of an alternative SBA-200E binary
  328. firmware image supplied by the user. This pathname may be
  329. absolute or relative to the drivers/atm directory.
  330. The driver comes with an adequate firmware image, so normal users do
  331. not have to supply an alternative one. They just say Y to "Use
  332. default SBA-200E firmware", above.
  333. config ATM_FORE200E_USE_TASKLET
  334. bool "Defer interrupt work to a tasklet"
  335. depends on (PCI || SBUS) && (ATM_FORE200E_PCA || ATM_FORE200E_SBA)
  336. default n
  337. help
  338. This defers work to be done by the interrupt handler to a
  339. tasklet instead of handling everything at interrupt time. This
  340. may improve the responsive of the host.
  341. config ATM_FORE200E_TX_RETRY
  342. int "Maximum number of tx retries"
  343. depends on (PCI || SBUS) && (ATM_FORE200E_PCA || ATM_FORE200E_SBA)
  344. default "16"
  345. ---help---
  346. Specifies the number of times the driver attempts to transmit
  347. a message before giving up, if the transmit queue of the ATM card
  348. is transiently saturated.
  349. Saturation of the transmit queue may occur only under extreme
  350. conditions, e.g. when a fast host continuously submits very small
  351. frames (<64 bytes) or raw AAL0 cells (48 bytes) to the ATM adapter.
  352. Note that under common conditions, it is unlikely that you encounter
  353. a saturation of the transmit queue, so the retry mechanism never
  354. comes into play.
  355. config ATM_FORE200E_DEBUG
  356. int "Debugging level (0-3)"
  357. depends on (PCI || SBUS) && (ATM_FORE200E_PCA || ATM_FORE200E_SBA)
  358. default "0"
  359. help
  360. Specifies the level of debugging messages issued by the driver.
  361. The verbosity of the driver increases with the value of this
  362. parameter.
  363. When active, these messages can have a significant impact on
  364. the performances of the driver, and the size of your syslog files!
  365. Keep the debugging level to 0 during normal operations.
  366. config ATM_FORE200E
  367. tristate
  368. depends on (PCI || SBUS) && (ATM_FORE200E_PCA || ATM_FORE200E_SBA)
  369. default m if ATM_FORE200E_MAYBE!=y
  370. default y if ATM_FORE200E_MAYBE=y
  371. config ATM_HE
  372. tristate "ForeRunner HE Series"
  373. depends on PCI && ATM
  374. help
  375. This is a driver for the Marconi ForeRunner HE-series ATM adapter
  376. cards. It simultaneously supports the 155 and 622 versions.
  377. config ATM_HE_USE_SUNI
  378. bool "Use S/UNI PHY driver"
  379. depends on ATM_HE
  380. help
  381. Support for the S/UNI-Ultra and S/UNI-622 found in the ForeRunner
  382. HE cards. This driver provides carrier detection some statistics.
  383. endmenu