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