Linux kernel mirror (for testing)
git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
tjh.dev
kernel
os
linux
1menu "Infrared-port device drivers"
2 depends on IRDA!=n
3
4comment "SIR device drivers"
5
6config 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
20config BFIN_SIR
21 tristate "Blackfin SIR on UART"
22 depends on BLACKFIN && IRDA
23 default n
24 help
25 Say Y here if your want to enable SIR function on Blackfin UART
26 devices.
27
28 To activate this driver you can start irattach like:
29 "irattach irda0 -s"
30
31 Saying M, it will be built as a module named bfin_sir.
32
33 Note that you need to turn off one of the serial drivers for SIR
34 to use that UART.
35
36config BFIN_SIR0
37 bool "Blackfin SIR on UART0"
38 depends on BFIN_SIR && !SERIAL_BFIN_UART0
39
40config BFIN_SIR1
41 bool "Blackfin SIR on UART1"
42 depends on BFIN_SIR && !SERIAL_BFIN_UART1 && (!BF531 && !BF532 && !BF533 && !BF561)
43
44config BFIN_SIR2
45 bool "Blackfin SIR on UART2"
46 depends on BFIN_SIR && !SERIAL_BFIN_UART2 && (BF54x || BF538 || BF539)
47
48config BFIN_SIR3
49 bool "Blackfin SIR on UART3"
50 depends on BFIN_SIR && !SERIAL_BFIN_UART3 && (BF54x)
51
52choice
53 prompt "SIR Mode"
54 depends on BFIN_SIR
55 default SIR_BFIN_DMA
56
57config SIR_BFIN_DMA
58 bool "DMA mode"
59 depends on !DMA_UNCACHED_NONE
60
61config SIR_BFIN_PIO
62 bool "PIO mode"
63endchoice
64
65comment "Dongle support"
66
67config DONGLE
68 bool "Serial dongle support"
69 depends on IRTTY_SIR
70 help
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.
74
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.
78
79config ESI_DONGLE
80 tristate "ESI JetEye PC dongle"
81 depends on IRTTY_SIR && DONGLE && IRDA
82 help
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:
88 "irattach -d esi".
89
90config ACTISYS_DONGLE
91 tristate "ACTiSYS IR-220L and IR220L+ dongle"
92 depends on IRTTY_SIR && DONGLE && IRDA
93 help
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+".
100
101config TEKRAM_DONGLE
102 tristate "Tekram IrMate 210B dongle"
103 depends on IRTTY_SIR && DONGLE && IRDA
104 help
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".
111
112config TOIM3232_DONGLE
113 tristate "TOIM3232 IrDa dongle"
114 depends on IRTTY_SIR && DONGLE && IRDA
115 help
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.
119
120config LITELINK_DONGLE
121 tristate "Parallax LiteLink dongle"
122 depends on IRTTY_SIR && DONGLE && IRDA
123 help
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".
130
131config MA600_DONGLE
132 tristate "Mobile Action MA600 dongle"
133 depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
134 help
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:
142 "irattach -d ma600".
143
144config GIRBIL_DONGLE
145 tristate "Greenwich GIrBIL dongle"
146 depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
147 help
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".
154
155config MCP2120_DONGLE
156 tristate "Microchip MCP2120"
157 depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
158 help
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".
165
166 You must build this dongle yourself. For more information see:
167 <http://www.eyetap.org/~tangf/irda_sir_linux.html>
168
169config OLD_BELKIN_DONGLE
170 tristate "Old Belkin dongle"
171 depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
172 help
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>.
177
178config ACT200L_DONGLE
179 tristate "ACTiSYS IR-200L dongle"
180 depends on IRTTY_SIR && DONGLE && IRDA && EXPERIMENTAL
181 help
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".
188
189config KINGSUN_DONGLE
190 tristate "KingSun/DonShine DS-620 IrDA-USB dongle"
191 depends on IRDA && USB && EXPERIMENTAL
192 help
193 Say Y or M here if you want to build support for the KingSun/DonShine
194 DS-620 IrDA-USB bridge device driver.
195
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).
199
200 To compile it as a module, choose M here: the module will be called
201 kingsun-sir.
202
203config EP7211_DONGLE
204 tristate "EP7211 I/R support"
205 depends on IRTTY_SIR && ARCH_EP7211 && IRDA && EXPERIMENTAL
206 help
207 Say Y here if you want to build support for the Cirrus logic
208 EP7211 chipset's infrared module.
209
210config KSDAZZLE_DONGLE
211 tristate "KingSun Dazzle IrDA-USB dongle (EXPERIMENTAL)"
212 depends on IRDA && USB && EXPERIMENTAL
213 help
214 Say Y or M here if you want to build support for the KingSun Dazzle
215 IrDA-USB bridge device driver.
216
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).
220
221 To compile it as a module, choose M here: the module will be called
222 ksdazzle-sir.
223
224config KS959_DONGLE
225 tristate "KingSun KS-959 IrDA-USB dongle (EXPERIMENTAL)"
226 depends on IRDA && USB && EXPERIMENTAL
227 help
228 Say Y or M here if you want to build support for the KingSun KS-959
229 IrDA-USB bridge device driver.
230
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).
234
235 To compile it as a module, choose M here: the module will be called
236 ks959-sir.
237
238comment "FIR device drivers"
239
240config USB_IRDA
241 tristate "IrDA USB dongles"
242 depends on IRDA && USB
243 select FW_LOADER
244 ---help---
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.
252
253 Please note that the driver is still experimental. And of course,
254 you will need both USB and IrDA support in your kernel...
255
256config SIGMATEL_FIR
257 tristate "SigmaTel STIr4200 bridge (EXPERIMENTAL)"
258 depends on IRDA && USB && EXPERIMENTAL
259 select CRC32
260 ---help---
261 Say Y here if you want to build support for the SigmaTel STIr4200
262 USB IrDA FIR bridge device driver.
263
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)
267 speeds.
268
269 To compile it as a module, choose M here: the module will be called
270 stir4200.
271
272config NSC_FIR
273 tristate "NSC PC87108/PC87338"
274 depends on IRDA && ISA_DMA_API
275 help
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.
279
280 To compile it as a module, choose M here: the module will be called
281 nsc-ircc.
282
283config WINBOND_FIR
284 tristate "Winbond W83977AF (IR)"
285 depends on IRDA && ISA_DMA_API
286 help
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
290 FIR (4Mbps) speeds.
291
292 To compile it as a module, choose M here: the module will be called
293 w83977af_ir.
294
295config TOSHIBA_FIR
296 tristate "Toshiba Type-O IR Port"
297 depends on IRDA && PCI && !64BIT && VIRT_TO_BUS
298 help
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
303 donauboe.
304
305config AU1000_FIR
306 tristate "Alchemy Au1000 SIR/FIR"
307 depends on SOC_AU1000 && IRDA
308
309config SMC_IRCC_FIR
310 tristate "SMSC IrCC (EXPERIMENTAL)"
311 depends on EXPERIMENTAL && IRDA && ISA_DMA_API
312 help
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
317 smsc-ircc2.o.
318
319config ALI_FIR
320 tristate "ALi M5123 FIR (EXPERIMENTAL)"
321 depends on EXPERIMENTAL && IRDA && ISA_DMA_API
322 help
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.
327
328 To compile it as a module, choose M here: the module will be called
329 ali-ircc.
330
331config VLSI_FIR
332 tristate "VLSI 82C147 SIR/MIR/FIR (EXPERIMENTAL)"
333 depends on EXPERIMENTAL && IRDA && PCI
334 help
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
338 FIR (4Mbps) speeds.
339
340 To compile it as a module, choose M here: the module will be called
341 vlsi_ir.
342
343config SA1100_FIR
344 tristate "SA1100 Internal IR"
345 depends on ARCH_SA1100 && IRDA
346
347config VIA_FIR
348 tristate "VIA VT8231/VT1211 SIR/MIR/FIR"
349 depends on IRDA && ISA_DMA_API
350 help
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.
357
358 You will need to specify the 'dongle_id' module parameter to
359 indicate the FIR dongle attached to the controller.
360
361 To compile it as a module, choose M here: the module will be called
362 via-ircc.
363
364config PXA_FICP
365 tristate "Intel PXA2xx Internal FICP"
366 depends on ARCH_PXA && IRDA
367 help
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
372 another.
373
374config MCS_FIR
375 tristate "MosChip MCS7780 IrDA-USB dongle"
376 depends on IRDA && USB && EXPERIMENTAL
377 select CRC32
378 help
379 Say Y or M here if you want to build support for the MosChip
380 MCS7780 IrDA-USB bridge device driver.
381
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)
385 speeds.
386
387 To compile it as a module, choose M here: the module will be called
388 mcs7780.
389
390endmenu
391