1 menu "Infrared-port device drivers"
4 comment "SIR device drivers"
7 tristate "IrTTY (uses Linux serial driver)"
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).
20 comment "Dongle support"
23 bool "Serial dongle support"
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.
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.
35 tristate "ESI JetEye PC dongle"
36 depends on IRTTY_SIR && DONGLE && IRDA
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:
46 tristate "ACTiSYS IR-220L and IR220L+ dongle"
47 depends on IRTTY_SIR && DONGLE && IRDA
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+".
57 tristate "Tekram IrMate 210B dongle"
58 depends on IRTTY_SIR && DONGLE && IRDA
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:
67 config TOIM3232_DONGLE
68 tristate "TOIM3232 IrDa dongle"
69 depends on IRTTY_SIR && DONGLE && IRDA
71 Say Y here if you want to build support for the Vishay/Temic
72 TOIM3232 and TOIM4232 based dongles.
73 To compile it as a module, choose M here.
75 config LITELINK_DONGLE
76 tristate "Parallax LiteLink dongle"
77 depends on IRTTY_SIR && DONGLE && IRDA
79 Say Y here if you want to build support for the Parallax Litelink
80 dongle. To compile it as a module, choose M here. The Parallax
81 dongle attaches to the normal 9-pin serial port connector, and can
82 currently only be used by IrTTY. To activate support for Parallax
83 dongles you will have to start irattach like this:
84 "irattach -d litelink".
87 tristate "Mobile Action MA600 dongle"
88 depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
90 Say Y here if you want to build support for the Mobile Action MA600
91 dongle. To compile it as a module, choose M here. The MA600 dongle
92 attaches to the normal 9-pin serial port connector, and can
93 currently only be used by IrTTY. The driver should also support
94 the MA620 USB version of the dongle, if the integrated USB-to-RS232
95 converter is supported by usbserial. To activate support for
96 MA600 dongle you will have to start irattach like this:
100 tristate "Greenwich GIrBIL dongle"
101 depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
103 Say Y here if you want to build support for the Greenwich GIrBIL
104 dongle. If you want to compile it as a module, choose M here.
105 The Greenwich dongle attaches to the normal 9-pin serial port
106 connector, and can currently only be used by IrTTY. To activate
107 support for Greenwich dongles you will have to start irattach
108 like this: "irattach -d girbil".
110 config MCP2120_DONGLE
111 tristate "Microchip MCP2120"
112 depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
114 Say Y here if you want to build support for the Microchip MCP2120
115 dongle. If you want to compile it as a module, choose M here.
116 The MCP2120 dongle attaches to the normal 9-pin serial port
117 connector, and can currently only be used by IrTTY. To activate
118 support for MCP2120 dongles you will have to start irattach
119 like this: "irattach -d mcp2120".
121 You must build this dongle yourself. For more information see:
122 <http://www.eyetap.org/~tangf/irda_sir_linux.html>
124 config OLD_BELKIN_DONGLE
125 tristate "Old Belkin dongle"
126 depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
128 Say Y here if you want to build support for the Adaptec Airport 1000
129 and 2000 dongles. If you want to compile it as a module, choose
130 M here. Some information is contained in the comments
131 at the top of <file:drivers/net/irda/old_belkin.c>.
133 config ACT200L_DONGLE
134 tristate "ACTiSYS IR-200L dongle"
135 depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
137 Say Y here if you want to build support for the ACTiSYS IR-200L
138 dongle. If you want to compile it as a module, choose M here.
139 The ACTiSYS IR-200L dongle attaches to the normal 9-pin serial
140 port connector, and can currently only be used by IrTTY.
141 To activate support for ACTiSYS IR-200L dongle you will have to
142 start irattach like this: "irattach -d act200l".
144 config KINGSUN_DONGLE
145 tristate "KingSun/DonShine DS-620 IrDA-USB dongle"
146 depends on IRDA && USB && EXPERIMENTAL
148 Say Y or M here if you want to build support for the KingSun/DonShine
149 DS-620 IrDA-USB bridge device driver.
151 This USB bridge does not conform to the IrDA-USB device class
152 specification, and therefore needs its own specific driver. This
153 dongle supports SIR speed only (9600 bps).
155 To compile it as a module, choose M here: the module will be called
159 tristate "EP7211 I/R support"
160 depends on IRTTY_SIR && ARCH_EP7211 && IRDA && EXPERIMENTAL
162 Say Y here if you want to build support for the Cirrus logic
163 EP7211 chipset's infrared module.
165 config KSDAZZLE_DONGLE
166 tristate "KingSun Dazzle IrDA-USB dongle (EXPERIMENTAL)"
167 depends on IRDA && USB && EXPERIMENTAL
169 Say Y or M here if you want to build support for the KingSun Dazzle
170 IrDA-USB bridge device driver.
172 This USB bridge does not conform to the IrDA-USB device class
173 specification, and therefore needs its own specific driver. This
174 dongle supports SIR speeds only (9600 through 115200 bps).
176 To compile it as a module, choose M here: the module will be called
180 tristate "KingSun KS-959 IrDA-USB dongle (EXPERIMENTAL)"
181 depends on IRDA && USB && EXPERIMENTAL
183 Say Y or M here if you want to build support for the KingSun KS-959
184 IrDA-USB bridge device driver.
186 This USB bridge does not conform to the IrDA-USB device class
187 specification, and therefore needs its own specific driver. This
188 dongle supports SIR speeds only (9600 through 57600 bps).
190 To compile it as a module, choose M here: the module will be called
193 comment "Old SIR device drivers"
196 tristate "IrPORT (IrDA serial driver)"
197 depends on IRDA && BROKEN_ON_SMP
199 Say Y here if you want to build support for the IrPORT IrDA device
200 driver. To compile it as a module, choose M here: the module will be
201 called irport. IrPORT can be used instead of IrTTY and sometimes
202 this can be better. One example is if your IrDA port does not
203 have echo-canceling, which will work OK with IrPORT since this
204 driver is working in half-duplex mode only. You don't need to use
205 irattach with IrPORT, but you just insert it the same way as FIR
206 drivers (insmod irport io=0x3e8 irq=11). Notice that IrPORT is a
207 SIR device driver which means that speed is limited to 115200 bps.
211 comment "Old Serial dongle support"
214 bool "Old Serial dongle support"
215 depends on IRPORT_SIR && BROKEN_ON_SMP
217 Say Y here if you have an infrared device that connects to your
218 computer's serial port. These devices are called dongles. Then say Y
219 or M to the driver for your particular dongle below.
221 Note that the answer to this question won't directly affect the
222 kernel: saying N will just cause the configurator to skip all
223 the questions about serial dongles.
225 config ESI_DONGLE_OLD
226 tristate "ESI JetEye PC dongle"
227 depends on DONGLE_OLD && IRDA
229 Say Y here if you want to build support for the Extended Systems
230 JetEye PC dongle. To compile it as a module, choose M here. The ESI
231 dongle attaches to the normal 9-pin serial port connector, and can
232 currently only be used by IrTTY. To activate support for ESI
233 dongles you will have to start irattach like this:
236 config ACTISYS_DONGLE_OLD
237 tristate "ACTiSYS IR-220L and IR220L+ dongle"
238 depends on DONGLE_OLD && IRDA
240 Say Y here if you want to build support for the ACTiSYS IR-220L and
241 IR220L+ dongles. To compile it as a module, choose M here. The
242 ACTiSYS dongles attaches to the normal 9-pin serial port connector,
243 and can currently only be used by IrTTY. To activate support for
244 ACTiSYS dongles you will have to start irattach like this:
245 "irattach -d actisys" or "irattach -d actisys+".
247 config TEKRAM_DONGLE_OLD
248 tristate "Tekram IrMate 210B dongle"
249 depends on DONGLE_OLD && IRDA
251 Say Y here if you want to build support for the Tekram IrMate 210B
252 dongle. To compile it as a module, choose M here. The Tekram dongle
253 attaches to the normal 9-pin serial port connector, and can
254 currently only be used by IrTTY. To activate support for Tekram
255 dongles you will have to start irattach like this:
256 "irattach -d tekram".
258 config GIRBIL_DONGLE_OLD
259 tristate "Greenwich GIrBIL dongle"
260 depends on DONGLE_OLD && IRDA
262 Say Y here if you want to build support for the Greenwich GIrBIL
263 dongle. To compile it as a module, choose M here. The Greenwich
264 dongle attaches to the normal 9-pin serial port connector, and can
265 currently only be used by IrTTY. To activate support for Greenwich
266 dongles you will have to insert "irattach -d girbil" in the
267 /etc/irda/drivers script.
269 config LITELINK_DONGLE_OLD
270 tristate "Parallax LiteLink dongle"
271 depends on DONGLE_OLD && IRDA
273 Say Y here if you want to build support for the Parallax Litelink
274 dongle. To compile it as a module, choose M here. The Parallax
275 dongle attaches to the normal 9-pin serial port connector, and can
276 currently only be used by IrTTY. To activate support for Parallax
277 dongles you will have to start irattach like this:
278 "irattach -d litelink".
280 config MCP2120_DONGLE_OLD
281 tristate "Microchip MCP2120"
282 depends on DONGLE_OLD && IRDA
284 Say Y here if you want to build support for the Microchip MCP2120
285 dongle. To compile it as a module, choose M here. The MCP2120 dongle
286 attaches to the normal 9-pin serial port connector, and can
287 currently only be used by IrTTY. To activate support for MCP2120
288 dongles you will have to insert "irattach -d mcp2120" in the
289 /etc/irda/drivers script.
291 You must build this dongle yourself. For more information see:
292 <http://www.eyetap.org/~tangf/irda_sir_linux.html>
294 config OLD_BELKIN_DONGLE_OLD
295 tristate "Old Belkin dongle"
296 depends on DONGLE_OLD && IRDA
298 Say Y here if you want to build support for the Adaptec Airport 1000
299 and 2000 dongles. To compile it as a module, choose M here: the module
300 will be called old_belkin. Some information is contained in the
301 comments at the top of <file:drivers/net/irda/old_belkin.c>.
303 config ACT200L_DONGLE_OLD
304 tristate "ACTiSYS IR-200L dongle (EXPERIMENTAL)"
305 depends on DONGLE_OLD && EXPERIMENTAL && IRDA
307 Say Y here if you want to build support for the ACTiSYS IR-200L
308 dongle. To compile it as a module, choose M here. The ACTiSYS
309 IR-200L dongle attaches to the normal 9-pin serial port connector,
310 and can currently only be used by IrTTY. To activate support for
311 ACTiSYS IR-200L dongles you will have to start irattach like this:
312 "irattach -d act200l".
314 config MA600_DONGLE_OLD
315 tristate "Mobile Action MA600 dongle (EXPERIMENTAL)"
316 depends on DONGLE_OLD && EXPERIMENTAL && IRDA
318 Say Y here if you want to build support for the Mobile Action MA600
319 dongle. To compile it as a module, choose M here. The MA600 dongle
320 attaches to the normal 9-pin serial port connector, and can
321 currently only be tested on IrCOMM. To activate support for MA600
322 dongles you will have to insert "irattach -d ma600" in the
323 /etc/irda/drivers script. Note: irutils 0.9.15 requires no
324 modification. irutils 0.9.9 needs modification. For more
325 information, download the following tar gzip file.
327 There is a pre-compiled module on
328 <http://engsvr.ust.hk/~eetwl95/ma600.html>
331 tristate "EP7211 I/R support"
332 depends on DONGLE_OLD && ARCH_EP7211 && IRDA
334 comment "FIR device drivers"
337 tristate "IrDA USB dongles"
338 depends on IRDA && USB
341 Say Y here if you want to build support for the USB IrDA FIR Dongle
342 device driver. To compile it as a module, choose M here: the module
343 will be called irda-usb. IrDA-USB support the various IrDA USB
344 dongles available and most of their peculiarities. Those dongles
345 plug in the USB port of your computer, are plug and play, and
346 support SIR and FIR (4Mbps) speeds. On the other hand, those
347 dongles tend to be less efficient than a FIR chipset.
349 Please note that the driver is still experimental. And of course,
350 you will need both USB and IrDA support in your kernel...
353 tristate "SigmaTel STIr4200 bridge (EXPERIMENTAL)"
354 depends on IRDA && USB && EXPERIMENTAL
357 Say Y here if you want to build support for the SigmaTel STIr4200
358 USB IrDA FIR bridge device driver.
360 USB bridge based on the SigmaTel STIr4200 don't conform to the
361 IrDA-USB device class specification, and therefore need their
362 own specific driver. Those dongles support SIR and FIR (4Mbps)
365 To compile it as a module, choose M here: the module will be called
369 tristate "NSC PC87108/PC87338"
370 depends on IRDA && ISA_DMA_API
372 Say Y here if you want to build support for the NSC PC87108 and
373 PC87338 IrDA chipsets. This driver supports SIR,
374 MIR and FIR (4Mbps) speeds.
376 To compile it as a module, choose M here: the module will be called
380 tristate "Winbond W83977AF (IR)"
381 depends on IRDA && ISA_DMA_API
383 Say Y here if you want to build IrDA support for the Winbond
384 W83977AF super-io chipset. This driver should be used for the IrDA
385 chipset in the Corel NetWinder. The driver supports SIR, MIR and
388 To compile it as a module, choose M here: the module will be called
392 tristate "Toshiba Type-O IR Port"
393 depends on IRDA && PCI && !64BIT && VIRT_TO_BUS
395 Say Y here if you want to build support for the Toshiba Type-O IR
396 and Donau oboe chipsets. These chipsets are used by the Toshiba
397 Libretto 100/110CT, Tecra 8100, Portege 7020 and many more laptops.
398 To compile it as a module, choose M here: the module will be called
402 tristate "Alchemy Au1000 SIR/FIR"
403 depends on SOC_AU1000 && IRDA
406 tristate "SMSC IrCC (EXPERIMENTAL)"
407 depends on EXPERIMENTAL && IRDA && ISA_DMA_API
409 Say Y here if you want to build support for the SMC Infrared
410 Communications Controller. It is used in a wide variety of
411 laptops (Fujitsu, Sony, Compaq and some Toshiba).
412 To compile it as a module, choose M here: the module will be called
416 tristate "ALi M5123 FIR (EXPERIMENTAL)"
417 depends on EXPERIMENTAL && IRDA && ISA_DMA_API
419 Say Y here if you want to build support for the ALi M5123 FIR
420 Controller. The ALi M5123 FIR Controller is embedded in ALi M1543C,
421 M1535, M1535D, M1535+, M1535D South Bridge. This driver supports
422 SIR, MIR and FIR (4Mbps) speeds.
424 To compile it as a module, choose M here: the module will be called
428 tristate "VLSI 82C147 SIR/MIR/FIR (EXPERIMENTAL)"
429 depends on EXPERIMENTAL && IRDA && PCI
431 Say Y here if you want to build support for the VLSI 82C147
432 PCI-IrDA Controller. This controller is used by the HP OmniBook 800
433 and 5500 notebooks. The driver provides support for SIR, MIR and
436 To compile it as a module, choose M here: the module will be called
440 tristate "SA1100 Internal IR"
441 depends on ARCH_SA1100 && IRDA
444 tristate "VIA VT8231/VT1211 SIR/MIR/FIR"
445 depends on IRDA && ISA_DMA_API
447 Say Y here if you want to build support for the VIA VT8231
448 and VIA VT1211 IrDA controllers, found on the motherboards using
449 those VIA chipsets. To use this controller, you will need
450 to plug a specific 5 pins FIR IrDA dongle in the specific
451 motherboard connector. The driver provides support for SIR, MIR
452 and FIR (4Mbps) speeds.
454 You will need to specify the 'dongle_id' module parameter to
455 indicate the FIR dongle attached to the controller.
457 To compile it as a module, choose M here: the module will be called
461 tristate "Intel PXA2xx Internal FICP"
462 depends on ARCH_PXA && IRDA
464 Say Y or M here if you want to build support for the PXA2xx
465 built-in IRDA interface which can support both SIR and FIR.
466 This driver relies on platform specific helper routines so
467 available capabilities may vary from one PXA2xx target to
471 tristate "MosChip MCS7780 IrDA-USB dongle"
472 depends on IRDA && USB && EXPERIMENTAL
474 Say Y or M here if you want to build support for the MosChip
475 MCS7780 IrDA-USB bridge device driver.
477 USB bridge based on the MosChip MCS7780 don't conform to the
478 IrDA-USB device class specification, and therefore need their
479 own specific driver. Those dongles support SIR and FIR (4Mbps)
482 To compile it as a module, choose M here: the module will be called