2 tristate "Remote Controller adapters"
6 Enable support for Remote Controllers on Linux. This is
7 needed in order to support several video capture adapters,
8 standalone IR receivers/transmitters, and RF receivers.
10 Enable this option if you have a video capture board even
11 if you don't need IR, as otherwise, you may not be able to
12 compile the driver for your adapter.
21 Enable this option to build the Linux Infrared Remote
22 Control (LIRC) core device interface driver. The LIRC
23 interface passes raw IR to and from userspace, where the
24 LIRC daemon handles protocol decoding for IR reception and
25 encoding for IR transmitting (aka "blasting").
27 source "drivers/media/rc/keymaps/Kconfig"
30 tristate "Enable IR raw decoder for the NEC protocol"
36 Enable this option if you have IR with NEC protocol, and
37 if the IR is decoded in software
40 tristate "Enable IR raw decoder for the RC-5 protocol"
46 Enable this option if you have IR with RC-5 protocol, and
47 if the IR is decoded in software
50 tristate "Enable IR raw decoder for the RC6 protocol"
56 Enable this option if you have an infrared remote control which
57 uses the RC6 protocol, and you need software decoding support.
60 tristate "Enable IR raw decoder for the JVC protocol"
66 Enable this option if you have an infrared remote control which
67 uses the JVC protocol, and you need software decoding support.
69 config IR_SONY_DECODER
70 tristate "Enable IR raw decoder for the Sony protocol"
75 Enable this option if you have an infrared remote control which
76 uses the Sony protocol, and you need software decoding support.
78 config IR_RC5_SZ_DECODER
79 tristate "Enable IR raw decoder for the RC-5 (streamzap) protocol"
85 Enable this option if you have IR with RC-5 (streamzap) protocol,
86 and if the IR is decoded in software. (The Streamzap PC Remote
87 uses an IR protocol that is almost standard RC-5, but not quite,
88 as it uses an additional bit).
90 config IR_SANYO_DECODER
91 tristate "Enable IR raw decoder for the Sanyo protocol"
96 Enable this option if you have an infrared remote control which
97 uses the Sanyo protocol (Sanyo, Aiwa, Chinon remotes),
98 and you need software decoding support.
100 config IR_MCE_KBD_DECODER
101 tristate "Enable IR raw decoder for the MCE keyboard/mouse protocol"
107 Enable this option if you have a Microsoft Remote Keyboard for
108 Windows Media Center Edition, which you would like to use with
109 a raw IR receiver in your system.
112 tristate "Enable IR to LIRC bridge"
118 Enable this option to pass raw IR to and from userspace via
122 tristate "ATI / X10 based USB RF remote controls"
123 depends on USB_ARCH_HAS_HCD
127 Say Y here if you want to use an X10 based USB remote control.
128 These are RF remotes with USB receivers.
130 Such devices include the ATI remote that comes with many of ATI's
131 All-In-Wonder video cards, the X10 "Lola" remote, NVIDIA RF remote,
132 Medion RF remote, and SnapStream FireFly remote.
134 This driver provides mouse pointer, left and right mouse buttons,
135 and maps all the other remote buttons to keypress events.
137 To compile this driver as a module, choose M here: the module will be
141 tristate "ENE eHome Receiver/Transceiver (pnp id: ENE0100/ENE02xxx)"
145 Say Y here to enable support for integrated infrared receiver
146 /transceiver made by ENE.
148 You can see if you have it by looking at lspnp output.
149 Output should include ENE0100 ENE0200 or something similar.
151 To compile this driver as a module, choose M here: the
152 module will be called ene_ir.
155 tristate "SoundGraph iMON Receiver and Display"
156 depends on USB_ARCH_HAS_HCD
160 Say Y here if you want to use a SoundGraph iMON (aka Antec Veris)
161 IR Receiver and/or LCD/VFD/VGA display.
163 To compile this driver as a module, choose M here: the
164 module will be called imon.
167 tristate "Windows Media Center Ed. eHome Infrared Transceiver"
168 depends on USB_ARCH_HAS_HCD
172 Say Y here if you want to use a Windows Media Center Edition
173 eHome Infrared Transceiver.
175 To compile this driver as a module, choose M here: the
176 module will be called mceusb.
179 tristate "ITE Tech Inc. IT8712/IT8512 Consumer Infrared Transceiver"
183 Say Y here to enable support for integrated infrared receivers
184 /transceivers made by ITE Tech Inc. These are found in
185 several ASUS devices, like the ASUS Digimatrix or the ASUS
188 To compile this driver as a module, choose M here: the
189 module will be called ite-cir.
192 tristate "Fintek Consumer Infrared Transceiver"
196 Say Y here to enable support for integrated infrared receiver
197 /transciever made by Fintek. This chip is found on assorted
198 Jetway motherboards (and of course, possibly others).
200 To compile this driver as a module, choose M here: the
201 module will be called fintek-cir.
204 tristate "Nuvoton w836x7hg Consumer Infrared Transceiver"
208 Say Y here to enable support for integrated infrared receiver
209 /transciever made by Nuvoton (formerly Winbond). This chip is
210 found in the ASRock ION 330HT, as well as assorted Intel
211 DP55-series motherboards (and of course, possibly others).
213 To compile this driver as a module, choose M here: the
214 module will be called nuvoton-cir.
217 tristate "RedRat3 IR Transceiver"
218 depends on USB_ARCH_HAS_HCD
222 Say Y here if you want to use a RedRat3 Infrared Transceiver.
224 To compile this driver as a module, choose M here: the
225 module will be called redrat3.
228 tristate "Streamzap PC Remote IR Receiver"
229 depends on USB_ARCH_HAS_HCD
233 Say Y here if you want to use a Streamzap PC Remote
236 To compile this driver as a module, choose M here: the
237 module will be called streamzap.
239 config IR_WINBOND_CIR
240 tristate "Winbond IR remote control"
241 depends on X86 && PNP
248 Say Y here if you want to use the IR remote functionality found
249 in some Winbond SuperI/O chips. Currently only the WPCD376I
250 chip is supported (included in some Intel Media series
253 To compile this driver as a module, choose M here: the module will
254 be called winbond_cir.
257 tristate "Remote Control Loopback Driver"
260 Say Y here if you want support for the remote control loopback
261 driver which allows TX data to be sent back as RX data.
262 This is mostly useful for debugging purposes.
264 If you're not sure, select N here.
266 To compile this driver as a module, choose M here: the module will
267 be called rc_loopback.