Kconfig 17 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451
  1. menu "Infrared-port device drivers"
  2. depends on IRDA!=n
  3. comment "SIR device drivers"
  4. config IRTTY_SIR
  5. tristate "IrTTY (uses Linux serial driver)"
  6. depends on IRDA
  7. help
  8. Say Y here if you want to build support for the IrTTY line
  9. discipline. To compile it as a module, choose M here: the module
  10. will be called irtty-sir. IrTTY makes it possible to use Linux's
  11. own serial driver for all IrDA ports that are 16550 compatible.
  12. Most IrDA chips are 16550 compatible so you should probably say Y
  13. to this option. Using IrTTY will however limit the speed of the
  14. connection to 115200 bps (IrDA SIR mode).
  15. If unsure, say Y.
  16. comment "Dongle support"
  17. config DONGLE
  18. bool "Serial dongle support"
  19. depends on IRTTY_SIR
  20. help
  21. Say Y here if you have an infrared device that connects to your
  22. computer's serial port. These devices are called dongles. Then say Y
  23. or M to the driver for your particular dongle below.
  24. Note that the answer to this question won't directly affect the
  25. kernel: saying N will just cause the configurator to skip all
  26. the questions about serial dongles.
  27. config ESI_DONGLE
  28. tristate "ESI JetEye PC dongle"
  29. depends on IRTTY_SIR && DONGLE && IRDA
  30. help
  31. Say Y here if you want to build support for the Extended Systems
  32. JetEye PC dongle. To compile it as a module, choose M here. The ESI
  33. dongle attaches to the normal 9-pin serial port connector, and can
  34. currently only be used by IrTTY. To activate support for ESI
  35. dongles you will have to start irattach like this:
  36. "irattach -d esi".
  37. config ACTISYS_DONGLE
  38. tristate "ACTiSYS IR-220L and IR220L+ dongle"
  39. depends on IRTTY_SIR && DONGLE && IRDA
  40. help
  41. Say Y here if you want to build support for the ACTiSYS IR-220L and
  42. IR220L+ dongles. To compile it as a module, choose M here. The
  43. ACTiSYS dongles attaches to the normal 9-pin serial port connector,
  44. and can currently only be used by IrTTY. To activate support for
  45. ACTiSYS dongles you will have to start irattach like this:
  46. "irattach -d actisys" or "irattach -d actisys+".
  47. config TEKRAM_DONGLE
  48. tristate "Tekram IrMate 210B dongle"
  49. depends on IRTTY_SIR && DONGLE && IRDA
  50. help
  51. Say Y here if you want to build support for the Tekram IrMate 210B
  52. dongle. To compile it as a module, choose M here. The Tekram dongle
  53. attaches to the normal 9-pin serial port connector, and can
  54. currently only be used by IrTTY. To activate support for Tekram
  55. dongles you will have to start irattach like this:
  56. "irattach -d tekram".
  57. config TOIM3232_DONGLE
  58. tristate "TOIM3232 IrDa dongle"
  59. depends on IRTTY_SIR && DONGLE && IRDA
  60. help
  61. Say Y here if you want to build support for the Vishay/Temic
  62. TOIM3232 and TOIM4232 based dongles.
  63. To compile it as a module, choose M here.
  64. config LITELINK_DONGLE
  65. tristate "Parallax LiteLink dongle"
  66. depends on IRTTY_SIR && DONGLE && IRDA
  67. help
  68. Say Y here if you want to build support for the Parallax Litelink
  69. dongle. To compile it as a module, choose M here. The Parallax
  70. dongle attaches to the normal 9-pin serial port connector, and can
  71. currently only be used by IrTTY. To activate support for Parallax
  72. dongles you will have to start irattach like this:
  73. "irattach -d litelink".
  74. config MA600_DONGLE
  75. tristate "Mobile Action MA600 dongle"
  76. depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
  77. help
  78. Say Y here if you want to build support for the Mobile Action MA600
  79. dongle. To compile it as a module, choose M here. The MA600 dongle
  80. attaches to the normal 9-pin serial port connector, and can
  81. currently only be used by IrTTY. The driver should also support
  82. the MA620 USB version of the dongle, if the integrated USB-to-RS232
  83. converter is supported by usbserial. To activate support for
  84. MA600 dongle you will have to start irattach like this:
  85. "irattach -d ma600".
  86. config GIRBIL_DONGLE
  87. tristate "Greenwich GIrBIL dongle"
  88. depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
  89. help
  90. Say Y here if you want to build support for the Greenwich GIrBIL
  91. dongle. If you want to compile it as a module, choose M here.
  92. The Greenwich dongle attaches to the normal 9-pin serial port
  93. connector, and can currently only be used by IrTTY. To activate
  94. support for Greenwich dongles you will have to start irattach
  95. like this: "irattach -d girbil".
  96. config MCP2120_DONGLE
  97. tristate "Microchip MCP2120"
  98. depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
  99. help
  100. Say Y here if you want to build support for the Microchip MCP2120
  101. dongle. If you want to compile it as a module, choose M here.
  102. The MCP2120 dongle attaches to the normal 9-pin serial port
  103. connector, and can currently only be used by IrTTY. To activate
  104. support for MCP2120 dongles you will have to start irattach
  105. like this: "irattach -d mcp2120".
  106. You must build this dongle yourself. For more information see:
  107. <http://www.eyetap.org/~tangf/irda_sir_linux.html>
  108. config OLD_BELKIN_DONGLE
  109. tristate "Old Belkin dongle"
  110. depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
  111. help
  112. Say Y here if you want to build support for the Adaptec Airport 1000
  113. and 2000 dongles. If you want to compile it as a module, choose
  114. M here. Some information is contained in the comments
  115. at the top of <file:drivers/net/irda/old_belkin.c>.
  116. config ACT200L_DONGLE
  117. tristate "ACTiSYS IR-200L dongle"
  118. depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
  119. help
  120. Say Y here if you want to build support for the ACTiSYS IR-200L
  121. dongle. If you want to compile it as a module, choose M here.
  122. The ACTiSYS IR-200L dongle attaches to the normal 9-pin serial
  123. port connector, and can currently only be used by IrTTY.
  124. To activate support for ACTiSYS IR-200L dongle you will have to
  125. start irattach like this: "irattach -d act200l".
  126. config KINGSUN_DONGLE
  127. tristate "KingSun/DonShine DS-620 IrDA-USB dongle"
  128. depends on IRDA && USB && EXPERIMENTAL
  129. help
  130. Say Y or M here if you want to build support for the KingSun/DonShine
  131. DS-620 IrDA-USB bridge device driver.
  132. This USB bridge does not conform to the IrDA-USB device class
  133. specification, and therefore needs its own specific driver. This
  134. dongle supports SIR speed only (9600 bps).
  135. To compile it as a module, choose M here: the module will be called
  136. kingsun-sir.
  137. comment "Old SIR device drivers"
  138. config IRPORT_SIR
  139. tristate "IrPORT (IrDA serial driver)"
  140. depends on IRDA && BROKEN_ON_SMP
  141. ---help---
  142. Say Y here if you want to build support for the IrPORT IrDA device
  143. driver. To compile it as a module, choose M here: the module will be
  144. called irport. IrPORT can be used instead of IrTTY and sometimes
  145. this can be better. One example is if your IrDA port does not
  146. have echo-canceling, which will work OK with IrPORT since this
  147. driver is working in half-duplex mode only. You don't need to use
  148. irattach with IrPORT, but you just insert it the same way as FIR
  149. drivers (insmod irport io=0x3e8 irq=11). Notice that IrPORT is a
  150. SIR device driver which means that speed is limited to 115200 bps.
  151. If unsure, say Y.
  152. comment "Old Serial dongle support"
  153. config DONGLE_OLD
  154. bool "Old Serial dongle support"
  155. depends on IRPORT_SIR && BROKEN_ON_SMP
  156. help
  157. Say Y here if you have an infrared device that connects to your
  158. computer's serial port. These devices are called dongles. Then say Y
  159. or M to the driver for your particular dongle below.
  160. Note that the answer to this question won't directly affect the
  161. kernel: saying N will just cause the configurator to skip all
  162. the questions about serial dongles.
  163. config ESI_DONGLE_OLD
  164. tristate "ESI JetEye PC dongle"
  165. depends on DONGLE_OLD && IRDA
  166. help
  167. Say Y here if you want to build support for the Extended Systems
  168. JetEye PC dongle. To compile it as a module, choose M here. The ESI
  169. dongle attaches to the normal 9-pin serial port connector, and can
  170. currently only be used by IrTTY. To activate support for ESI
  171. dongles you will have to start irattach like this:
  172. "irattach -d esi".
  173. config ACTISYS_DONGLE_OLD
  174. tristate "ACTiSYS IR-220L and IR220L+ dongle"
  175. depends on DONGLE_OLD && IRDA
  176. help
  177. Say Y here if you want to build support for the ACTiSYS IR-220L and
  178. IR220L+ dongles. To compile it as a module, choose M here. The
  179. ACTiSYS dongles attaches to the normal 9-pin serial port connector,
  180. and can currently only be used by IrTTY. To activate support for
  181. ACTiSYS dongles you will have to start irattach like this:
  182. "irattach -d actisys" or "irattach -d actisys+".
  183. config TEKRAM_DONGLE_OLD
  184. tristate "Tekram IrMate 210B dongle"
  185. depends on DONGLE_OLD && IRDA
  186. help
  187. Say Y here if you want to build support for the Tekram IrMate 210B
  188. dongle. To compile it as a module, choose M here. The Tekram dongle
  189. attaches to the normal 9-pin serial port connector, and can
  190. currently only be used by IrTTY. To activate support for Tekram
  191. dongles you will have to start irattach like this:
  192. "irattach -d tekram".
  193. config GIRBIL_DONGLE_OLD
  194. tristate "Greenwich GIrBIL dongle"
  195. depends on DONGLE_OLD && IRDA
  196. help
  197. Say Y here if you want to build support for the Greenwich GIrBIL
  198. dongle. To compile it as a module, choose M here. The Greenwich
  199. dongle attaches to the normal 9-pin serial port connector, and can
  200. currently only be used by IrTTY. To activate support for Greenwich
  201. dongles you will have to insert "irattach -d girbil" in the
  202. /etc/irda/drivers script.
  203. config LITELINK_DONGLE_OLD
  204. tristate "Parallax LiteLink dongle"
  205. depends on DONGLE_OLD && IRDA
  206. help
  207. Say Y here if you want to build support for the Parallax Litelink
  208. dongle. To compile it as a module, choose M here. The Parallax
  209. dongle attaches to the normal 9-pin serial port connector, and can
  210. currently only be used by IrTTY. To activate support for Parallax
  211. dongles you will have to start irattach like this:
  212. "irattach -d litelink".
  213. config MCP2120_DONGLE_OLD
  214. tristate "Microchip MCP2120"
  215. depends on DONGLE_OLD && IRDA
  216. help
  217. Say Y here if you want to build support for the Microchip MCP2120
  218. dongle. To compile it as a module, choose M here. The MCP2120 dongle
  219. attaches to the normal 9-pin serial port connector, and can
  220. currently only be used by IrTTY. To activate support for MCP2120
  221. dongles you will have to insert "irattach -d mcp2120" in the
  222. /etc/irda/drivers script.
  223. You must build this dongle yourself. For more information see:
  224. <http://www.eyetap.org/~tangf/irda_sir_linux.html>
  225. config OLD_BELKIN_DONGLE_OLD
  226. tristate "Old Belkin dongle"
  227. depends on DONGLE_OLD && IRDA
  228. help
  229. Say Y here if you want to build support for the Adaptec Airport 1000
  230. and 2000 dongles. To compile it as a module, choose M here: the module
  231. will be called old_belkin. Some information is contained in the
  232. comments at the top of <file:drivers/net/irda/old_belkin.c>.
  233. config ACT200L_DONGLE_OLD
  234. tristate "ACTiSYS IR-200L dongle (EXPERIMENTAL)"
  235. depends on DONGLE_OLD && EXPERIMENTAL && IRDA
  236. help
  237. Say Y here if you want to build support for the ACTiSYS IR-200L
  238. dongle. To compile it as a module, choose M here. The ACTiSYS
  239. IR-200L dongle attaches to the normal 9-pin serial port connector,
  240. and can currently only be used by IrTTY. To activate support for
  241. ACTiSYS IR-200L dongles you will have to start irattach like this:
  242. "irattach -d act200l".
  243. config MA600_DONGLE_OLD
  244. tristate "Mobile Action MA600 dongle (EXPERIMENTAL)"
  245. depends on DONGLE_OLD && EXPERIMENTAL && IRDA
  246. ---help---
  247. Say Y here if you want to build support for the Mobile Action MA600
  248. dongle. To compile it as a module, choose M here. The MA600 dongle
  249. attaches to the normal 9-pin serial port connector, and can
  250. currently only be tested on IrCOMM. To activate support for MA600
  251. dongles you will have to insert "irattach -d ma600" in the
  252. /etc/irda/drivers script. Note: irutils 0.9.15 requires no
  253. modification. irutils 0.9.9 needs modification. For more
  254. information, download the following tar gzip file.
  255. There is a pre-compiled module on
  256. <http://engsvr.ust.hk/~eetwl95/ma600.html>
  257. config EP7211_IR
  258. tristate "EP7211 I/R support"
  259. depends on DONGLE_OLD && ARCH_EP7211 && IRDA
  260. comment "FIR device drivers"
  261. config USB_IRDA
  262. tristate "IrDA USB dongles"
  263. depends on IRDA && USB
  264. select FW_LOADER
  265. ---help---
  266. Say Y here if you want to build support for the USB IrDA FIR Dongle
  267. device driver. To compile it as a module, choose M here: the module
  268. will be called irda-usb. IrDA-USB support the various IrDA USB
  269. dongles available and most of their peculiarities. Those dongles
  270. plug in the USB port of your computer, are plug and play, and
  271. support SIR and FIR (4Mbps) speeds. On the other hand, those
  272. dongles tend to be less efficient than a FIR chipset.
  273. Please note that the driver is still experimental. And of course,
  274. you will need both USB and IrDA support in your kernel...
  275. config SIGMATEL_FIR
  276. tristate "SigmaTel STIr4200 bridge (EXPERIMENTAL)"
  277. depends on IRDA && USB && EXPERIMENTAL
  278. select CRC32
  279. ---help---
  280. Say Y here if you want to build support for the SigmaTel STIr4200
  281. USB IrDA FIR bridge device driver.
  282. USB bridge based on the SigmaTel STIr4200 don't conform to the
  283. IrDA-USB device class specification, and therefore need their
  284. own specific driver. Those dongles support SIR and FIR (4Mbps)
  285. speeds.
  286. To compile it as a module, choose M here: the module will be called
  287. stir4200.
  288. config NSC_FIR
  289. tristate "NSC PC87108/PC87338"
  290. depends on IRDA && ISA_DMA_API
  291. help
  292. Say Y here if you want to build support for the NSC PC87108 and
  293. PC87338 IrDA chipsets. This driver supports SIR,
  294. MIR and FIR (4Mbps) speeds.
  295. To compile it as a module, choose M here: the module will be called
  296. nsc-ircc.
  297. config WINBOND_FIR
  298. tristate "Winbond W83977AF (IR)"
  299. depends on IRDA && ISA_DMA_API
  300. help
  301. Say Y here if you want to build IrDA support for the Winbond
  302. W83977AF super-io chipset. This driver should be used for the IrDA
  303. chipset in the Corel NetWinder. The driver supports SIR, MIR and
  304. FIR (4Mbps) speeds.
  305. To compile it as a module, choose M here: the module will be called
  306. w83977af_ir.
  307. config TOSHIBA_FIR
  308. tristate "Toshiba Type-O IR Port"
  309. depends on IRDA && PCI && !64BIT
  310. help
  311. Say Y here if you want to build support for the Toshiba Type-O IR
  312. and Donau oboe chipsets. These chipsets are used by the Toshiba
  313. Libretto 100/110CT, Tecra 8100, Portege 7020 and many more laptops.
  314. To compile it as a module, choose M here: the module will be called
  315. donauboe.
  316. config AU1000_FIR
  317. tristate "Alchemy Au1000 SIR/FIR"
  318. depends on SOC_AU1000 && IRDA
  319. config SMC_IRCC_FIR
  320. tristate "SMSC IrCC (EXPERIMENTAL)"
  321. depends on EXPERIMENTAL && IRDA && ISA_DMA_API
  322. help
  323. Say Y here if you want to build support for the SMC Infrared
  324. Communications Controller. It is used in a wide variety of
  325. laptops (Fujitsu, Sony, Compaq and some Toshiba).
  326. To compile it as a module, choose M here: the module will be called
  327. smsc-ircc2.o.
  328. config ALI_FIR
  329. tristate "ALi M5123 FIR (EXPERIMENTAL)"
  330. depends on EXPERIMENTAL && IRDA && ISA_DMA_API
  331. help
  332. Say Y here if you want to build support for the ALi M5123 FIR
  333. Controller. The ALi M5123 FIR Controller is embedded in ALi M1543C,
  334. M1535, M1535D, M1535+, M1535D South Bridge. This driver supports
  335. SIR, MIR and FIR (4Mbps) speeds.
  336. To compile it as a module, choose M here: the module will be called
  337. ali-ircc.
  338. config VLSI_FIR
  339. tristate "VLSI 82C147 SIR/MIR/FIR (EXPERIMENTAL)"
  340. depends on EXPERIMENTAL && IRDA && PCI
  341. help
  342. Say Y here if you want to build support for the VLSI 82C147
  343. PCI-IrDA Controller. This controller is used by the HP OmniBook 800
  344. and 5500 notebooks. The driver provides support for SIR, MIR and
  345. FIR (4Mbps) speeds.
  346. To compile it as a module, choose M here: the module will be called
  347. vlsi_ir.
  348. config SA1100_FIR
  349. tristate "SA1100 Internal IR"
  350. depends on ARCH_SA1100 && IRDA
  351. config VIA_FIR
  352. tristate "VIA VT8231/VT1211 SIR/MIR/FIR"
  353. depends on IRDA && ISA_DMA_API
  354. help
  355. Say Y here if you want to build support for the VIA VT8231
  356. and VIA VT1211 IrDA controllers, found on the motherboards using
  357. those VIA chipsets. To use this controller, you will need
  358. to plug a specific 5 pins FIR IrDA dongle in the specific
  359. motherboard connector. The driver provides support for SIR, MIR
  360. and FIR (4Mbps) speeds.
  361. You will need to specify the 'dongle_id' module parameter to
  362. indicate the FIR dongle attached to the controller.
  363. To compile it as a module, choose M here: the module will be called
  364. via-ircc.
  365. config PXA_FICP
  366. tristate "Intel PXA2xx Internal FICP"
  367. depends on ARCH_PXA && IRDA
  368. help
  369. Say Y or M here if you want to build support for the PXA2xx
  370. built-in IRDA interface which can support both SIR and FIR.
  371. This driver relies on platform specific helper routines so
  372. available capabilities may vary from one PXA2xx target to
  373. another.
  374. config MCS_FIR
  375. tristate "MosChip MCS7780 IrDA-USB dongle"
  376. depends on IRDA && USB && EXPERIMENTAL
  377. help
  378. Say Y or M here if you want to build support for the MosChip
  379. MCS7780 IrDA-USB bridge device driver.
  380. USB bridge based on the MosChip MCS7780 don't conform to the
  381. IrDA-USB device class specification, and therefore need their
  382. own specific driver. Those dongles support SIR and FIR (4Mbps)
  383. speeds.
  384. To compile it as a module, choose M here: the module will be called
  385. mcs7780.
  386. endmenu