Kconfig 16 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499
  1. #
  2. # wan devices configuration
  3. #
  4. menuconfig WAN
  5. bool "Wan interfaces support"
  6. ---help---
  7. Wide Area Networks (WANs), such as X.25, Frame Relay and leased
  8. lines, are used to interconnect Local Area Networks (LANs) over vast
  9. distances with data transfer rates significantly higher than those
  10. achievable with commonly used asynchronous modem connections.
  11. Usually, a quite expensive external device called a `WAN router' is
  12. needed to connect to a WAN. As an alternative, a relatively
  13. inexpensive WAN interface card can allow your Linux box to directly
  14. connect to a WAN.
  15. If you have one of those cards and wish to use it under Linux,
  16. say Y here and also to the WAN driver for your card.
  17. If unsure, say N.
  18. if WAN
  19. # There is no way to detect a comtrol sv11 - force it modular for now.
  20. config HOSTESS_SV11
  21. tristate "Comtrol Hostess SV-11 support"
  22. depends on ISA && m && ISA_DMA_API && INET
  23. help
  24. Driver for Comtrol Hostess SV-11 network card which
  25. operates on low speed synchronous serial links at up to
  26. 256Kbps, supporting PPP and Cisco HDLC.
  27. The driver will be compiled as a module: the
  28. module will be called hostess_sv11.
  29. # The COSA/SRP driver has not been tested as non-modular yet.
  30. config COSA
  31. tristate "COSA/SRP sync serial boards support"
  32. depends on ISA && m && ISA_DMA_API
  33. ---help---
  34. Driver for COSA and SRP synchronous serial boards.
  35. These boards allow to connect synchronous serial devices (for example
  36. base-band modems, or any other device with the X.21, V.24, V.35 or
  37. V.36 interface) to your Linux box. The cards can work as the
  38. character device, synchronous PPP network device, or the Cisco HDLC
  39. network device.
  40. You will need user-space utilities COSA or SRP boards for downloading
  41. the firmware to the cards and to set them up. Look at the
  42. <http://www.fi.muni.cz/~kas/cosa/> for more information. You can also
  43. read the comment at the top of the <file:drivers/net/wan/cosa.c> for
  44. details about the cards and the driver itself.
  45. The driver will be compiled as a module: the
  46. module will be called cosa.
  47. #
  48. # Lan Media's board. Currently 1000, 1200, 5200, 5245
  49. #
  50. config LANMEDIA
  51. tristate "LanMedia Corp. SSI/V.35, T1/E1, HSSI, T3 boards"
  52. depends on PCI && VIRT_TO_BUS
  53. ---help---
  54. Driver for the following Lan Media family of serial boards:
  55. - LMC 1000 board allows you to connect synchronous serial devices
  56. (for example base-band modems, or any other device with the X.21,
  57. V.24, V.35 or V.36 interface) to your Linux box.
  58. - LMC 1200 with on board DSU board allows you to connect your Linux
  59. box directly to a T1 or E1 circuit.
  60. - LMC 5200 board provides a HSSI interface capable of running up to
  61. 52 Mbits per second.
  62. - LMC 5245 board connects directly to a T3 circuit saving the
  63. additional external hardware.
  64. To change setting such as syncPPP vs Cisco HDLC or clock source you
  65. will need lmcctl. It is available at <ftp://ftp.lanmedia.com/>
  66. (broken link).
  67. To compile this driver as a module, choose M here: the
  68. module will be called lmc.
  69. # There is no way to detect a Sealevel board. Force it modular
  70. config SEALEVEL_4021
  71. tristate "Sealevel Systems 4021 support"
  72. depends on ISA && m && ISA_DMA_API && INET
  73. help
  74. This is a driver for the Sealevel Systems ACB 56 serial I/O adapter.
  75. The driver will be compiled as a module: the
  76. module will be called sealevel.
  77. # Generic HDLC
  78. config HDLC
  79. tristate "Generic HDLC layer"
  80. help
  81. Say Y to this option if your Linux box contains a WAN (Wide Area
  82. Network) card supported by this driver and you are planning to
  83. connect the box to a WAN.
  84. You will need supporting software from
  85. <http://www.kernel.org/pub/linux/utils/net/hdlc/>.
  86. Generic HDLC driver currently supports raw HDLC, Cisco HDLC, Frame
  87. Relay, synchronous Point-to-Point Protocol (PPP) and X.25.
  88. To compile this driver as a module, choose M here: the
  89. module will be called hdlc.
  90. If unsure, say N.
  91. config HDLC_RAW
  92. tristate "Raw HDLC support"
  93. depends on HDLC
  94. help
  95. Generic HDLC driver supporting raw HDLC over WAN connections.
  96. If unsure, say N.
  97. config HDLC_RAW_ETH
  98. tristate "Raw HDLC Ethernet device support"
  99. depends on HDLC
  100. help
  101. Generic HDLC driver supporting raw HDLC Ethernet device emulation
  102. over WAN connections.
  103. You will need it for Ethernet over HDLC bridges.
  104. If unsure, say N.
  105. config HDLC_CISCO
  106. tristate "Cisco HDLC support"
  107. depends on HDLC
  108. help
  109. Generic HDLC driver supporting Cisco HDLC over WAN connections.
  110. If unsure, say N.
  111. config HDLC_FR
  112. tristate "Frame Relay support"
  113. depends on HDLC
  114. help
  115. Generic HDLC driver supporting Frame Relay over WAN connections.
  116. If unsure, say N.
  117. config HDLC_PPP
  118. tristate "Synchronous Point-to-Point Protocol (PPP) support"
  119. depends on HDLC
  120. help
  121. Generic HDLC driver supporting PPP over WAN connections.
  122. It will be replaced by new PPP implementation in Linux 2.6.26.
  123. If unsure, say N.
  124. config HDLC_X25
  125. tristate "X.25 protocol support"
  126. depends on HDLC && (LAPB=m && HDLC=m || LAPB=y)
  127. help
  128. Generic HDLC driver supporting X.25 over WAN connections.
  129. If unsure, say N.
  130. comment "X.25/LAPB support is disabled"
  131. depends on HDLC && (LAPB!=m || HDLC!=m) && LAPB!=y
  132. config PCI200SYN
  133. tristate "Goramo PCI200SYN support"
  134. depends on HDLC && PCI
  135. help
  136. Driver for PCI200SYN cards by Goramo sp. j.
  137. If you have such a card, say Y here and see
  138. <http://www.kernel.org/pub/linux/utils/net/hdlc/>.
  139. To compile this as a module, choose M here: the
  140. module will be called pci200syn.
  141. If unsure, say N.
  142. config WANXL
  143. tristate "SBE Inc. wanXL support"
  144. depends on HDLC && PCI
  145. help
  146. Driver for wanXL PCI cards by SBE Inc.
  147. If you have such a card, say Y here and see
  148. <http://www.kernel.org/pub/linux/utils/net/hdlc/>.
  149. To compile this as a module, choose M here: the
  150. module will be called wanxl.
  151. If unsure, say N.
  152. config WANXL_BUILD_FIRMWARE
  153. bool "rebuild wanXL firmware"
  154. depends on WANXL && !PREVENT_FIRMWARE_BUILD
  155. help
  156. Allows you to rebuild firmware run by the QUICC processor.
  157. It requires as68k, ld68k and hexdump programs.
  158. You should never need this option, say N.
  159. config PC300
  160. tristate "Cyclades-PC300 support (RS-232/V.35, X.21, T1/E1 boards)"
  161. depends on HDLC && PCI
  162. ---help---
  163. Driver for the Cyclades-PC300 synchronous communication boards.
  164. These boards provide synchronous serial interfaces to your
  165. Linux box (interfaces currently available are RS-232/V.35, X.21 and
  166. T1/E1). If you wish to support Multilink PPP, please select the
  167. option later and read the file README.mlppp provided by PC300
  168. package.
  169. To compile this as a module, choose M here: the module
  170. will be called pc300.
  171. If unsure, say N.
  172. config PC300_MLPPP
  173. bool "Cyclades-PC300 MLPPP support"
  174. depends on PC300 && PPP_MULTILINK && PPP_SYNC_TTY && HDLC_PPP
  175. help
  176. Multilink PPP over the PC300 synchronous communication boards.
  177. comment "Cyclades-PC300 MLPPP support is disabled."
  178. depends on HDLC && PC300 && (PPP=n || !PPP_MULTILINK || PPP_SYNC_TTY=n || !HDLC_PPP)
  179. comment "Refer to the file README.mlppp, provided by PC300 package."
  180. depends on HDLC && PC300 && (PPP=n || !PPP_MULTILINK || PPP_SYNC_TTY=n || !HDLC_PPP)
  181. config PC300TOO
  182. tristate "Cyclades PC300 RSV/X21 alternative support"
  183. depends on HDLC && PCI
  184. help
  185. Alternative driver for PC300 RSV/X21 PCI cards made by
  186. Cyclades, Inc. If you have such a card, say Y here and see
  187. <http://www.kernel.org/pub/linux/utils/net/hdlc/>.
  188. To compile this as a module, choose M here: the module
  189. will be called pc300too.
  190. If unsure, say N here.
  191. config N2
  192. tristate "SDL RISCom/N2 support"
  193. depends on HDLC && ISA
  194. help
  195. Driver for RISCom/N2 single or dual channel ISA cards by
  196. SDL Communications Inc.
  197. If you have such a card, say Y here and see
  198. <http://www.kernel.org/pub/linux/utils/net/hdlc/>.
  199. Note that N2csu and N2dds cards are not supported by this driver.
  200. To compile this driver as a module, choose M here: the module
  201. will be called n2.
  202. If unsure, say N.
  203. config C101
  204. tristate "Moxa C101 support"
  205. depends on HDLC && ISA
  206. help
  207. Driver for C101 SuperSync ISA cards by Moxa Technologies Co., Ltd.
  208. If you have such a card, say Y here and see
  209. <http://www.kernel.org/pub/linux/utils/net/hdlc/>.
  210. To compile this driver as a module, choose M here: the
  211. module will be called c101.
  212. If unsure, say N.
  213. config FARSYNC
  214. tristate "FarSync T-Series support"
  215. depends on HDLC && PCI
  216. ---help---
  217. Support for the FarSync T-Series X.21 (and V.35/V.24) cards by
  218. FarSite Communications Ltd.
  219. Synchronous communication is supported on all ports at speeds up to
  220. 8Mb/s (128K on V.24) using synchronous PPP, Cisco HDLC, raw HDLC,
  221. Frame Relay or X.25/LAPB.
  222. If you want the module to be automatically loaded when the interface
  223. is referenced then you should add "alias hdlcX farsync" to
  224. /etc/modprobe.conf for each interface, where X is 0, 1, 2, ..., or
  225. simply use "alias hdlc* farsync" to indicate all of them.
  226. To compile this driver as a module, choose M here: the
  227. module will be called farsync.
  228. config DSCC4
  229. tristate "Etinc PCISYNC serial board support"
  230. depends on HDLC && PCI && m
  231. help
  232. Driver for Etinc PCISYNC boards based on the Infineon (ex. Siemens)
  233. DSCC4 chipset.
  234. This is supposed to work with the four port card. Take a look at
  235. <http://www.cogenit.fr/dscc4/> for further information about the
  236. driver.
  237. To compile this driver as a module, choose M here: the
  238. module will be called dscc4.
  239. config DSCC4_PCISYNC
  240. bool "Etinc PCISYNC features"
  241. depends on DSCC4
  242. help
  243. Due to Etinc's design choice for its PCISYNC cards, some operations
  244. are only allowed on specific ports of the DSCC4. This option is the
  245. only way for the driver to know that it shouldn't return a success
  246. code for these operations.
  247. Please say Y if your card is an Etinc's PCISYNC.
  248. config DSCC4_PCI_RST
  249. bool "Hard reset support"
  250. depends on DSCC4
  251. help
  252. Various DSCC4 bugs forbid any reliable software reset of the ASIC.
  253. As a replacement, some vendors provide a way to assert the PCI #RST
  254. pin of DSCC4 through the GPIO port of the card. If you choose Y,
  255. the driver will make use of this feature before module removal
  256. (i.e. rmmod). The feature is known to be available on Commtech's
  257. cards. Contact your manufacturer for details.
  258. Say Y if your card supports this feature.
  259. config DLCI
  260. tristate "Frame Relay DLCI support"
  261. ---help---
  262. Support for the Frame Relay protocol.
  263. Frame Relay is a fast low-cost way to connect to a remote Internet
  264. access provider or to form a private wide area network. The one
  265. physical line from your box to the local "switch" (i.e. the entry
  266. point to the Frame Relay network, usually at the phone company) can
  267. carry several logical point-to-point connections to other computers
  268. connected to the Frame Relay network. For a general explanation of
  269. the protocol, check out <http://www.mplsforum.org/>.
  270. To use frame relay, you need supporting hardware (called FRAD) and
  271. certain programs from the net-tools package as explained in
  272. <file:Documentation/networking/framerelay.txt>.
  273. To compile this driver as a module, choose M here: the
  274. module will be called dlci.
  275. config DLCI_MAX
  276. int "Max DLCI per device"
  277. depends on DLCI
  278. default "8"
  279. help
  280. How many logical point-to-point frame relay connections (the
  281. identifiers of which are called DCLIs) should be handled by each
  282. of your hardware frame relay access devices.
  283. Go with the default.
  284. config SDLA
  285. tristate "SDLA (Sangoma S502/S508) support"
  286. depends on DLCI && ISA
  287. help
  288. Driver for the Sangoma S502A, S502E, and S508 Frame Relay Access
  289. Devices.
  290. These are multi-protocol cards, but only Frame Relay is supported
  291. by the driver at this time. Please read
  292. <file:Documentation/networking/framerelay.txt>.
  293. To compile this driver as a module, choose M here: the
  294. module will be called sdla.
  295. # Wan router core.
  296. config WAN_ROUTER_DRIVERS
  297. tristate "WAN router drivers"
  298. depends on WAN_ROUTER
  299. ---help---
  300. Connect LAN to WAN via Linux box.
  301. Select driver your card and remember to say Y to "Wan Router."
  302. You will need the wan-tools package which is available from
  303. <ftp://ftp.sangoma.com/>. For more information read:
  304. <file:Documentation/networking/wan-router.txt>.
  305. Note that the answer to this question won't directly affect the
  306. kernel except for how subordinate drivers may be built:
  307. saying N will just cause the configurator to skip all
  308. the questions about WAN router drivers.
  309. If unsure, say N.
  310. config CYCLADES_SYNC
  311. tristate "Cyclom 2X(tm) cards (EXPERIMENTAL)"
  312. depends on WAN_ROUTER_DRIVERS && (PCI || ISA)
  313. ---help---
  314. Cyclom 2X from Cyclades Corporation <http://www.cyclades.com/> is an
  315. intelligent multiprotocol WAN adapter with data transfer rates up to
  316. 512 Kbps. These cards support the X.25 and SNA related protocols.
  317. While no documentation is available at this time please grab the
  318. wanconfig tarball in
  319. <http://www.conectiva.com.br/~acme/cycsyn-devel/> (with minor changes
  320. to make it compile with the current wanrouter include files; efforts
  321. are being made to use the original package available at
  322. <ftp://ftp.sangoma.com/>).
  323. Feel free to contact me or the cycsyn-devel mailing list at
  324. <acme@conectiva.com.br> and <cycsyn-devel@bazar.conectiva.com.br> for
  325. additional details, I hope to have documentation available as soon as
  326. possible. (Cyclades Brazil is writing the Documentation).
  327. The next questions will ask you about the protocols you want the
  328. driver to support (for now only X.25 is supported).
  329. If you have one or more of these cards, say Y to this option.
  330. To compile this driver as a module, choose M here: the
  331. module will be called cyclomx.
  332. config CYCLOMX_X25
  333. bool "Cyclom 2X X.25 support (EXPERIMENTAL)"
  334. depends on CYCLADES_SYNC
  335. help
  336. Connect a Cyclom 2X card to an X.25 network.
  337. Enabling X.25 support will enlarge your kernel by about 11 kB.
  338. # X.25 network drivers
  339. config LAPBETHER
  340. tristate "LAPB over Ethernet driver (EXPERIMENTAL)"
  341. depends on LAPB && X25
  342. ---help---
  343. Driver for a pseudo device (typically called /dev/lapb0) which allows
  344. you to open an LAPB point-to-point connection to some other computer
  345. on your Ethernet network.
  346. In order to do this, you need to say Y or M to the driver for your
  347. Ethernet card as well as to "LAPB Data Link Driver".
  348. To compile this driver as a module, choose M here: the
  349. module will be called lapbether.
  350. If unsure, say N.
  351. config X25_ASY
  352. tristate "X.25 async driver (EXPERIMENTAL)"
  353. depends on LAPB && X25
  354. ---help---
  355. Send and receive X.25 frames over regular asynchronous serial
  356. lines such as telephone lines equipped with ordinary modems.
  357. Experts should note that this driver doesn't currently comply with
  358. the asynchronous HDLS framing protocols in CCITT recommendation X.25.
  359. To compile this driver as a module, choose M here: the
  360. module will be called x25_asy.
  361. If unsure, say N.
  362. config SBNI
  363. tristate "Granch SBNI12 Leased Line adapter support"
  364. depends on X86
  365. ---help---
  366. Driver for ISA SBNI12-xx cards which are low cost alternatives to
  367. leased line modems.
  368. You can find more information and last versions of drivers and
  369. utilities at <http://www.granch.ru/>. If you have any question you
  370. can send email to <sbni@granch.ru>.
  371. To compile this driver as a module, choose M here: the
  372. module will be called sbni.
  373. If unsure, say N.
  374. config SBNI_MULTILINE
  375. bool "Multiple line feature support"
  376. depends on SBNI
  377. help
  378. Schedule traffic for some parallel lines, via SBNI12 adapters.
  379. If you have two computers connected with two parallel lines it's
  380. possible to increase transfer rate nearly twice. You should have
  381. a program named 'sbniconfig' to configure adapters.
  382. If unsure, say N.
  383. endif # WAN