Kconfig 16 KB

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