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).
21 tristate "Blackfin SIR on UART"
22 depends on BLACKFIN && IRDA
25 Say Y here if your want to enable SIR function on Blackfin UART
28 To activate this driver you can start irattach like:
31 Saying M, it will be built as a module named bfin_sir.
33 Note that you need to turn off one of the serial drivers for SIR
37 bool "Blackfin SIR on UART0"
38 depends on BFIN_SIR && !SERIAL_BFIN_UART0
41 bool "Blackfin SIR on UART1"
42 depends on BFIN_SIR && !SERIAL_BFIN_UART1 && (!BF531 && !BF532 && !BF533 && !BF561)
45 bool "Blackfin SIR on UART2"
46 depends on BFIN_SIR && !SERIAL_BFIN_UART2 && (BF54x || BF538 || BF539)
49 bool "Blackfin SIR on UART3"
50 depends on BFIN_SIR && !SERIAL_BFIN_UART3 && (BF54x)
59 depends on !DMA_UNCACHED_NONE
65 comment "Dongle support"
68 bool "Serial dongle support"
71 Say Y here if you have an infrared device that connects to your
72 computer's serial port. These devices are called dongles. Then say Y
73 or M to the driver for your particular dongle below.
75 Note that the answer to this question won't directly affect the
76 kernel: saying N will just cause the configurator to skip all
77 the questions about serial dongles.
80 tristate "ESI JetEye PC dongle"
81 depends on IRTTY_SIR && DONGLE && IRDA
83 Say Y here if you want to build support for the Extended Systems
84 JetEye PC dongle. To compile it as a module, choose M here. The ESI
85 dongle attaches to the normal 9-pin serial port connector, and can
86 currently only be used by IrTTY. To activate support for ESI
87 dongles you will have to start irattach like this:
91 tristate "ACTiSYS IR-220L and IR220L+ dongle"
92 depends on IRTTY_SIR && DONGLE && IRDA
94 Say Y here if you want to build support for the ACTiSYS IR-220L and
95 IR220L+ dongles. To compile it as a module, choose M here. The
96 ACTiSYS dongles attaches to the normal 9-pin serial port connector,
97 and can currently only be used by IrTTY. To activate support for
98 ACTiSYS dongles you will have to start irattach like this:
99 "irattach -d actisys" or "irattach -d actisys+".
102 tristate "Tekram IrMate 210B dongle"
103 depends on IRTTY_SIR && DONGLE && IRDA
105 Say Y here if you want to build support for the Tekram IrMate 210B
106 dongle. To compile it as a module, choose M here. The Tekram dongle
107 attaches to the normal 9-pin serial port connector, and can
108 currently only be used by IrTTY. To activate support for Tekram
109 dongles you will have to start irattach like this:
110 "irattach -d tekram".
112 config TOIM3232_DONGLE
113 tristate "TOIM3232 IrDa dongle"
114 depends on IRTTY_SIR && DONGLE && IRDA
116 Say Y here if you want to build support for the Vishay/Temic
117 TOIM3232 and TOIM4232 based dongles.
118 To compile it as a module, choose M here.
120 config LITELINK_DONGLE
121 tristate "Parallax LiteLink dongle"
122 depends on IRTTY_SIR && DONGLE && IRDA
124 Say Y here if you want to build support for the Parallax Litelink
125 dongle. To compile it as a module, choose M here. The Parallax
126 dongle attaches to the normal 9-pin serial port connector, and can
127 currently only be used by IrTTY. To activate support for Parallax
128 dongles you will have to start irattach like this:
129 "irattach -d litelink".
132 tristate "Mobile Action MA600 dongle"
133 depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
135 Say Y here if you want to build support for the Mobile Action MA600
136 dongle. To compile it as a module, choose M here. The MA600 dongle
137 attaches to the normal 9-pin serial port connector, and can
138 currently only be used by IrTTY. The driver should also support
139 the MA620 USB version of the dongle, if the integrated USB-to-RS232
140 converter is supported by usbserial. To activate support for
141 MA600 dongle you will have to start irattach like this:
145 tristate "Greenwich GIrBIL dongle"
146 depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
148 Say Y here if you want to build support for the Greenwich GIrBIL
149 dongle. If you want to compile it as a module, choose M here.
150 The Greenwich dongle attaches to the normal 9-pin serial port
151 connector, and can currently only be used by IrTTY. To activate
152 support for Greenwich dongles you will have to start irattach
153 like this: "irattach -d girbil".
155 config MCP2120_DONGLE
156 tristate "Microchip MCP2120"
157 depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
159 Say Y here if you want to build support for the Microchip MCP2120
160 dongle. If you want to compile it as a module, choose M here.
161 The MCP2120 dongle attaches to the normal 9-pin serial port
162 connector, and can currently only be used by IrTTY. To activate
163 support for MCP2120 dongles you will have to start irattach
164 like this: "irattach -d mcp2120".
166 You must build this dongle yourself. For more information see:
167 <http://www.eyetap.org/~tangf/irda_sir_linux.html>
169 config OLD_BELKIN_DONGLE
170 tristate "Old Belkin dongle"
171 depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
173 Say Y here if you want to build support for the Adaptec Airport 1000
174 and 2000 dongles. If you want to compile it as a module, choose
175 M here. Some information is contained in the comments
176 at the top of <file:drivers/net/irda/old_belkin.c>.
178 config ACT200L_DONGLE
179 tristate "ACTiSYS IR-200L dongle"
180 depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
182 Say Y here if you want to build support for the ACTiSYS IR-200L
183 dongle. If you want to compile it as a module, choose M here.
184 The ACTiSYS IR-200L dongle attaches to the normal 9-pin serial
185 port connector, and can currently only be used by IrTTY.
186 To activate support for ACTiSYS IR-200L dongle you will have to
187 start irattach like this: "irattach -d act200l".
189 config KINGSUN_DONGLE
190 tristate "KingSun/DonShine DS-620 IrDA-USB dongle"
191 depends on IRDA && USB && EXPERIMENTAL
193 Say Y or M here if you want to build support for the KingSun/DonShine
194 DS-620 IrDA-USB bridge device driver.
196 This USB bridge does not conform to the IrDA-USB device class
197 specification, and therefore needs its own specific driver. This
198 dongle supports SIR speed only (9600 bps).
200 To compile it as a module, choose M here: the module will be called
204 tristate "EP7211 I/R support"
205 depends on IRTTY_SIR && ARCH_EP7211 && IRDA && EXPERIMENTAL
207 Say Y here if you want to build support for the Cirrus logic
208 EP7211 chipset's infrared module.
210 config KSDAZZLE_DONGLE
211 tristate "KingSun Dazzle IrDA-USB dongle (EXPERIMENTAL)"
212 depends on IRDA && USB && EXPERIMENTAL
214 Say Y or M here if you want to build support for the KingSun Dazzle
215 IrDA-USB bridge device driver.
217 This USB bridge does not conform to the IrDA-USB device class
218 specification, and therefore needs its own specific driver. This
219 dongle supports SIR speeds only (9600 through 115200 bps).
221 To compile it as a module, choose M here: the module will be called
225 tristate "KingSun KS-959 IrDA-USB dongle (EXPERIMENTAL)"
226 depends on IRDA && USB && EXPERIMENTAL
228 Say Y or M here if you want to build support for the KingSun KS-959
229 IrDA-USB bridge device driver.
231 This USB bridge does not conform to the IrDA-USB device class
232 specification, and therefore needs its own specific driver. This
233 dongle supports SIR speeds only (9600 through 57600 bps).
235 To compile it as a module, choose M here: the module will be called
238 comment "FIR device drivers"
241 tristate "IrDA USB dongles"
242 depends on IRDA && USB
245 Say Y here if you want to build support for the USB IrDA FIR Dongle
246 device driver. To compile it as a module, choose M here: the module
247 will be called irda-usb. IrDA-USB support the various IrDA USB
248 dongles available and most of their peculiarities. Those dongles
249 plug in the USB port of your computer, are plug and play, and
250 support SIR and FIR (4Mbps) speeds. On the other hand, those
251 dongles tend to be less efficient than a FIR chipset.
253 Please note that the driver is still experimental. And of course,
254 you will need both USB and IrDA support in your kernel...
257 tristate "SigmaTel STIr4200 bridge (EXPERIMENTAL)"
258 depends on IRDA && USB && EXPERIMENTAL
261 Say Y here if you want to build support for the SigmaTel STIr4200
262 USB IrDA FIR bridge device driver.
264 USB bridge based on the SigmaTel STIr4200 don't conform to the
265 IrDA-USB device class specification, and therefore need their
266 own specific driver. Those dongles support SIR and FIR (4Mbps)
269 To compile it as a module, choose M here: the module will be called
273 tristate "NSC PC87108/PC87338"
274 depends on IRDA && ISA_DMA_API
276 Say Y here if you want to build support for the NSC PC87108 and
277 PC87338 IrDA chipsets. This driver supports SIR,
278 MIR and FIR (4Mbps) speeds.
280 To compile it as a module, choose M here: the module will be called
284 tristate "Winbond W83977AF (IR)"
285 depends on IRDA && ISA_DMA_API
287 Say Y here if you want to build IrDA support for the Winbond
288 W83977AF super-io chipset. This driver should be used for the IrDA
289 chipset in the Corel NetWinder. The driver supports SIR, MIR and
292 To compile it as a module, choose M here: the module will be called
296 tristate "Toshiba Type-O IR Port"
297 depends on IRDA && PCI && !64BIT && VIRT_TO_BUS
299 Say Y here if you want to build support for the Toshiba Type-O IR
300 and Donau oboe chipsets. These chipsets are used by the Toshiba
301 Libretto 100/110CT, Tecra 8100, Portege 7020 and many more laptops.
302 To compile it as a module, choose M here: the module will be called
306 tristate "Alchemy Au1000 SIR/FIR"
307 depends on SOC_AU1000 && IRDA
310 tristate "SMSC IrCC (EXPERIMENTAL)"
311 depends on EXPERIMENTAL && IRDA && ISA_DMA_API
313 Say Y here if you want to build support for the SMC Infrared
314 Communications Controller. It is used in a wide variety of
315 laptops (Fujitsu, Sony, Compaq and some Toshiba).
316 To compile it as a module, choose M here: the module will be called
320 tristate "ALi M5123 FIR (EXPERIMENTAL)"
321 depends on EXPERIMENTAL && IRDA && ISA_DMA_API
323 Say Y here if you want to build support for the ALi M5123 FIR
324 Controller. The ALi M5123 FIR Controller is embedded in ALi M1543C,
325 M1535, M1535D, M1535+, M1535D South Bridge. This driver supports
326 SIR, MIR and FIR (4Mbps) speeds.
328 To compile it as a module, choose M here: the module will be called
332 tristate "VLSI 82C147 SIR/MIR/FIR (EXPERIMENTAL)"
333 depends on EXPERIMENTAL && IRDA && PCI
335 Say Y here if you want to build support for the VLSI 82C147
336 PCI-IrDA Controller. This controller is used by the HP OmniBook 800
337 and 5500 notebooks. The driver provides support for SIR, MIR and
340 To compile it as a module, choose M here: the module will be called
344 tristate "SA1100 Internal IR"
345 depends on ARCH_SA1100 && IRDA
348 tristate "VIA VT8231/VT1211 SIR/MIR/FIR"
349 depends on IRDA && ISA_DMA_API
351 Say Y here if you want to build support for the VIA VT8231
352 and VIA VT1211 IrDA controllers, found on the motherboards using
353 those VIA chipsets. To use this controller, you will need
354 to plug a specific 5 pins FIR IrDA dongle in the specific
355 motherboard connector. The driver provides support for SIR, MIR
356 and FIR (4Mbps) speeds.
358 You will need to specify the 'dongle_id' module parameter to
359 indicate the FIR dongle attached to the controller.
361 To compile it as a module, choose M here: the module will be called
365 tristate "Intel PXA2xx Internal FICP"
366 depends on ARCH_PXA && IRDA
368 Say Y or M here if you want to build support for the PXA2xx
369 built-in IRDA interface which can support both SIR and FIR.
370 This driver relies on platform specific helper routines so
371 available capabilities may vary from one PXA2xx target to
375 tristate "MosChip MCS7780 IrDA-USB dongle"
376 depends on IRDA && USB && EXPERIMENTAL
379 Say Y or M here if you want to build support for the MosChip
380 MCS7780 IrDA-USB bridge device driver.
382 USB bridge based on the MosChip MCS7780 don't conform to the
383 IrDA-USB device class specification, and therefore need their
384 own specific driver. Those dongles support SIR and FIR (4Mbps)
387 To compile it as a module, choose M here: the module will be called