Kconfig 16 KB

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