]>
Commit | Line | Data |
---|---|---|
1da177e4 LT |
1 | # |
2 | # USB Input driver configuration | |
3 | # | |
4 | comment "USB Input Devices" | |
5 | depends on USB | |
6 | ||
7 | config USB_HID | |
8 | tristate "USB Human Interface Device (full HID) support" | |
63f3861d JK |
9 | default y |
10 | depends on USB && HID | |
1da177e4 | 11 | ---help--- |
63f3861d | 12 | Say Y here if you want full HID support to connect USB keyboards, |
1da177e4 LT |
13 | mice, joysticks, graphic tablets, or any other HID based devices |
14 | to your computer via USB. You also need to select HID Input layer | |
15 | support (below) if you want to use keyboards, mice, joysticks and | |
16 | the like ... as well as Uninterruptible Power Supply (UPS) and | |
17 | monitor control devices. | |
18 | ||
19 | You can't use this driver and the HIDBP (Boot Protocol) keyboard | |
20 | and mouse drivers at the same time. More information is available: | |
21 | <file:Documentation/input/input.txt>. | |
22 | ||
23 | If unsure, say Y. | |
24 | ||
25 | To compile this driver as a module, choose M here: the | |
26 | module will be called usbhid. | |
27 | ||
28 | comment "Input core support is needed for USB HID input layer or HIDBP support" | |
29 | depends on USB_HID && INPUT=n | |
30 | ||
63f3861d | 31 | config USB_HID_POWERBOOK |
eab9edd2 MH |
32 | bool "Enable support for iBook/PowerBook special keys" |
33 | default n | |
63f3861d | 34 | depends on USB_HID |
eab9edd2 MH |
35 | help |
36 | Say Y here if you want support for the special keys (Fn, Numlock) on | |
37 | Apple iBooks and PowerBooks. | |
38 | ||
39 | If unsure, say N. | |
40 | ||
1da177e4 LT |
41 | config HID_FF |
42 | bool "Force feedback support (EXPERIMENTAL)" | |
63f3861d | 43 | depends on USB_HID && EXPERIMENTAL |
1da177e4 LT |
44 | help |
45 | Say Y here is you want force feedback support for a few HID devices. | |
46 | See below for a list of supported devices. | |
47 | ||
48 | See <file:Documentation/input/ff.txt> for a description of the force | |
49 | feedback API. | |
50 | ||
51 | If unsure, say N. | |
52 | ||
53 | config HID_PID | |
224ee88f | 54 | bool "PID device support" |
1da177e4 LT |
55 | depends on HID_FF |
56 | help | |
224ee88f AH |
57 | Say Y here if you have a PID-compliant device and wish to enable force |
58 | feedback for it. Microsoft Sidewinder Force Feedback 2 is one of such | |
59 | devices. | |
1da177e4 LT |
60 | |
61 | config LOGITECH_FF | |
62 | bool "Logitech WingMan *3D support" | |
63 | depends on HID_FF | |
dc76c912 | 64 | select INPUT_FF_MEMLESS if USB_HID |
1da177e4 LT |
65 | help |
66 | Say Y here if you have one of these devices: | |
67 | - Logitech WingMan Cordless RumblePad | |
68 | - Logitech WingMan Force 3D | |
69 | and if you want to enable force feedback for them. | |
70 | Note: if you say N here, this device will still be supported, but without | |
71 | force feedback. | |
72 | ||
73 | config THRUSTMASTER_FF | |
74 | bool "ThrustMaster FireStorm Dual Power 2 support (EXPERIMENTAL)" | |
75 | depends on HID_FF && EXPERIMENTAL | |
dc76c912 | 76 | select INPUT_FF_MEMLESS if USB_HID |
1da177e4 LT |
77 | help |
78 | Say Y here if you have a THRUSTMASTER FireStore Dual Power 2, | |
79 | and want to enable force feedback support for it. | |
80 | Note: if you say N here, this device will still be supported, but without | |
81 | force feedback. | |
82 | ||
bb3caf7f AH |
83 | config ZEROPLUS_FF |
84 | bool "Zeroplus based game controller support" | |
85 | depends on HID_FF | |
86 | select INPUT_FF_MEMLESS if USB_HID | |
87 | help | |
88 | Say Y here if you have a Zeroplus based game controller and want to | |
89 | enable force feedback for it. | |
90 | ||
1da177e4 LT |
91 | config USB_HIDDEV |
92 | bool "/dev/hiddev raw HID device support" | |
93 | depends on USB_HID | |
94 | help | |
95 | Say Y here if you want to support HID devices (from the USB | |
96 | specification standpoint) that aren't strictly user interface | |
97 | devices, like monitor controls and Uninterruptable Power Supplies. | |
98 | ||
99 | This module supports these devices separately using a separate | |
100 | event interface on /dev/usb/hiddevX (char 180:96 to 180:111). | |
101 | ||
102 | If unsure, say Y. | |
103 | ||
104 | menu "USB HID Boot Protocol drivers" | |
105 | depends on USB!=n && USB_HID!=y | |
106 | ||
107 | config USB_KBD | |
108 | tristate "USB HIDBP Keyboard (simple Boot) support" | |
109 | depends on USB && INPUT | |
110 | ---help--- | |
111 | Say Y here only if you are absolutely sure that you don't want | |
112 | to use the generic HID driver for your USB keyboard and prefer | |
113 | to use the keyboard in its limited Boot Protocol mode instead. | |
114 | ||
115 | This is almost certainly not what you want. This is mostly | |
116 | useful for embedded applications or simple keyboards. | |
117 | ||
118 | To compile this driver as a module, choose M here: the | |
119 | module will be called usbkbd. | |
120 | ||
121 | If even remotely unsure, say N. | |
122 | ||
123 | config USB_MOUSE | |
124 | tristate "USB HIDBP Mouse (simple Boot) support" | |
125 | depends on USB && INPUT | |
126 | ---help--- | |
127 | Say Y here only if you are absolutely sure that you don't want | |
128 | to use the generic HID driver for your USB mouse and prefer | |
129 | to use the mouse in its limited Boot Protocol mode instead. | |
130 | ||
131 | This is almost certainly not what you want. This is mostly | |
132 | useful for embedded applications or simple mice. | |
133 | ||
134 | To compile this driver as a module, choose M here: the | |
135 | module will be called usbmouse. | |
136 | ||
137 | If even remotely unsure, say N. | |
138 | ||
139 | endmenu | |
140 | ||
141 | config USB_AIPTEK | |
142 | tristate "Aiptek 6000U/8000U tablet support" | |
143 | depends on USB && INPUT | |
144 | help | |
145 | Say Y here if you want to use the USB version of the Aiptek 6000U | |
146 | or Aiptek 8000U tablet. Make sure to say Y to "Mouse support" | |
147 | (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" | |
148 | (CONFIG_INPUT_EVDEV) as well. | |
149 | ||
150 | To compile this driver as a module, choose M here: the | |
151 | module will be called aiptek. | |
152 | ||
153 | config USB_WACOM | |
154 | tristate "Wacom Intuos/Graphire tablet support" | |
155 | depends on USB && INPUT | |
156 | help | |
157 | Say Y here if you want to use the USB version of the Wacom Intuos | |
158 | or Graphire tablet. Make sure to say Y to "Mouse support" | |
159 | (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" | |
160 | (CONFIG_INPUT_EVDEV) as well. | |
161 | ||
162 | To compile this driver as a module, choose M here: the | |
163 | module will be called wacom. | |
164 | ||
53880546 SV |
165 | config USB_ACECAD |
166 | tristate "Acecad Flair tablet support" | |
167 | depends on USB && INPUT | |
168 | help | |
169 | Say Y here if you want to use the USB version of the Acecad Flair | |
170 | tablet. Make sure to say Y to "Mouse support" | |
171 | (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" | |
172 | (CONFIG_INPUT_EVDEV) as well. | |
173 | ||
174 | To compile this driver as a module, choose M here: the | |
175 | module will be called acecad. | |
176 | ||
1da177e4 LT |
177 | config USB_KBTAB |
178 | tristate "KB Gear JamStudio tablet support" | |
179 | depends on USB && INPUT | |
180 | help | |
181 | Say Y here if you want to use the USB version of the KB Gear | |
182 | JamStudio tablet. Make sure to say Y to "Mouse support" | |
183 | (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" | |
184 | (CONFIG_INPUT_EVDEV) as well. | |
185 | ||
186 | To compile this driver as a module, choose M here: the | |
187 | module will be called kbtab. | |
188 | ||
189 | config USB_POWERMATE | |
190 | tristate "Griffin PowerMate and Contour Jog support" | |
191 | depends on USB && INPUT | |
192 | ---help--- | |
193 | Say Y here if you want to use Griffin PowerMate or Contour Jog devices. | |
194 | These are aluminum dials which can measure clockwise and anticlockwise | |
195 | rotation. The dial also acts as a pushbutton. The base contains an LED | |
196 | which can be instructed to pulse or to switch to a particular intensity. | |
197 | ||
198 | You can download userspace tools from | |
199 | <http://sowerbutts.com/powermate/>. | |
200 | ||
201 | To compile this driver as a module, choose M here: the | |
202 | module will be called powermate. | |
203 | ||
1d3e2023 DR |
204 | config USB_TOUCHSCREEN |
205 | tristate "USB Touchscreen Driver" | |
206 | depends on USB && INPUT | |
207 | ---help--- | |
208 | USB Touchscreen driver for: | |
5d892665 | 209 | - eGalax Touchkit USB (also includes eTurboTouch CT-410/510/700) |
1d3e2023 | 210 | - PanJit TouchSet USB |
5d892665 | 211 | - 3M MicroTouch USB (EX II series) |
1d3e2023 | 212 | - ITM |
5d892665 DR |
213 | - some other eTurboTouch |
214 | - Gunze AHL61 | |
24ced062 | 215 | - DMC TSC-10/25 |
1d3e2023 DR |
216 | |
217 | Have a look at <http://linux.chapter7.ch/touchkit/> for | |
218 | a usage description and the required user-space stuff. | |
219 | ||
220 | To compile this driver as a module, choose M here: the | |
221 | module will be called usbtouchscreen. | |
222 | ||
223 | config USB_TOUCHSCREEN_EGALAX | |
224 | default y | |
5d892665 | 225 | bool "eGalax, eTurboTouch CT-410/510/700 device support" if EMBEDDED |
1d3e2023 DR |
226 | depends on USB_TOUCHSCREEN |
227 | ||
228 | config USB_TOUCHSCREEN_PANJIT | |
229 | default y | |
230 | bool "PanJit device support" if EMBEDDED | |
231 | depends on USB_TOUCHSCREEN | |
232 | ||
233 | config USB_TOUCHSCREEN_3M | |
234 | default y | |
5d892665 | 235 | bool "3M/Microtouch EX II series device support" if EMBEDDED |
1d3e2023 DR |
236 | depends on USB_TOUCHSCREEN |
237 | ||
238 | config USB_TOUCHSCREEN_ITM | |
239 | default y | |
240 | bool "ITM device support" if EMBEDDED | |
241 | depends on USB_TOUCHSCREEN | |
242 | ||
5d892665 DR |
243 | config USB_TOUCHSCREEN_ETURBO |
244 | default y | |
245 | bool "eTurboTouch (non-eGalax compatible) device support" if EMBEDDED | |
246 | depends on USB_TOUCHSCREEN | |
247 | ||
248 | config USB_TOUCHSCREEN_GUNZE | |
249 | default y | |
250 | bool "Gunze AHL61 device support" if EMBEDDED | |
251 | depends on USB_TOUCHSCREEN | |
252 | ||
24ced062 HS |
253 | config USB_TOUCHSCREEN_DMC_TSC10 |
254 | default y | |
255 | bool "DMC TSC-10/25 device support" if EMBEDDED | |
256 | depends on USB_TOUCHSCREEN | |
257 | ||
aca951a2 HV |
258 | config USB_YEALINK |
259 | tristate "Yealink usb-p1k voip phone" | |
260 | depends on USB && INPUT && EXPERIMENTAL | |
261 | ---help--- | |
262 | Say Y here if you want to enable keyboard and LCD functions of the | |
263 | Yealink usb-p1k usb phones. The audio part is enabled by the generic | |
264 | usb sound driver, so you might want to enable that as well. | |
265 | ||
266 | For information about how to use these additional functions, see | |
267 | <file:Documentation/input/yealink.txt>. | |
268 | ||
269 | To compile this driver as a module, choose M here: the module will be | |
270 | called yealink. | |
271 | ||
1da177e4 LT |
272 | config USB_XPAD |
273 | tristate "X-Box gamepad support" | |
274 | depends on USB && INPUT | |
275 | ---help--- | |
276 | Say Y here if you want to use the X-Box pad with your computer. | |
277 | Make sure to say Y to "Joystick support" (CONFIG_INPUT_JOYDEV) | |
278 | and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well. | |
279 | ||
280 | For information about how to connect the X-Box pad to USB, see | |
281 | <file:Documentation/input/xpad.txt>. | |
282 | ||
283 | To compile this driver as a module, choose M here: the | |
284 | module will be called xpad. | |
285 | ||
286 | config USB_ATI_REMOTE | |
287 | tristate "ATI / X10 USB RF remote control" | |
288 | depends on USB && INPUT | |
289 | ---help--- | |
290 | Say Y here if you want to use an ATI or X10 "Lola" USB remote control. | |
291 | These are RF remotes with USB receivers. | |
292 | The ATI remote comes with many of ATI's All-In-Wonder video cards. | |
293 | The X10 "Lola" remote is available at: | |
294 | <http://www.x10.com/products/lola_sg1.htm> | |
295 | This driver provides mouse pointer, left and right mouse buttons, | |
296 | and maps all the other remote buttons to keypress events. | |
297 | ||
298 | To compile this driver as a module, choose M here: the module will be | |
299 | called ati_remote. | |
300 | ||