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" | |
9 | depends on USB | |
10 | ---help--- | |
11 | Say Y here if you want full HID support to connect keyboards, | |
12 | mice, joysticks, graphic tablets, or any other HID based devices | |
13 | to your computer via USB. You also need to select HID Input layer | |
14 | support (below) if you want to use keyboards, mice, joysticks and | |
15 | the like ... as well as Uninterruptible Power Supply (UPS) and | |
16 | monitor control devices. | |
17 | ||
18 | You can't use this driver and the HIDBP (Boot Protocol) keyboard | |
19 | and mouse drivers at the same time. More information is available: | |
20 | <file:Documentation/input/input.txt>. | |
21 | ||
22 | If unsure, say Y. | |
23 | ||
24 | To compile this driver as a module, choose M here: the | |
25 | module will be called usbhid. | |
26 | ||
27 | comment "Input core support is needed for USB HID input layer or HIDBP support" | |
28 | depends on USB_HID && INPUT=n | |
29 | ||
30 | config USB_HIDINPUT | |
31 | bool "HID input layer support" | |
32 | default y | |
33 | depends on INPUT && USB_HID | |
34 | help | |
35 | Say Y here if you want to use a USB keyboard, mouse or joystick, | |
36 | or any other HID input device. | |
37 | ||
38 | If unsure, say Y. | |
39 | ||
40 | config HID_FF | |
41 | bool "Force feedback support (EXPERIMENTAL)" | |
42 | depends on USB_HIDINPUT && EXPERIMENTAL | |
43 | help | |
44 | Say Y here is you want force feedback support for a few HID devices. | |
45 | See below for a list of supported devices. | |
46 | ||
47 | See <file:Documentation/input/ff.txt> for a description of the force | |
48 | feedback API. | |
49 | ||
50 | If unsure, say N. | |
51 | ||
52 | config HID_PID | |
53 | bool "PID Devices (Microsoft Sidewinder Force Feedback 2)" | |
54 | depends on HID_FF | |
55 | help | |
56 | Say Y here if you have a PID-compliant joystick and wish to enable force | |
57 | feedback for it. The Microsoft Sidewinder Force Feedback 2 is one such | |
58 | device. | |
59 | ||
60 | config LOGITECH_FF | |
61 | bool "Logitech WingMan *3D support" | |
62 | depends on HID_FF | |
63 | help | |
64 | Say Y here if you have one of these devices: | |
65 | - Logitech WingMan Cordless RumblePad | |
66 | - Logitech WingMan Force 3D | |
67 | and if you want to enable force feedback for them. | |
68 | Note: if you say N here, this device will still be supported, but without | |
69 | force feedback. | |
70 | ||
71 | config THRUSTMASTER_FF | |
72 | bool "ThrustMaster FireStorm Dual Power 2 support (EXPERIMENTAL)" | |
73 | depends on HID_FF && EXPERIMENTAL | |
74 | help | |
75 | Say Y here if you have a THRUSTMASTER FireStore Dual Power 2, | |
76 | and want to enable force feedback support for it. | |
77 | Note: if you say N here, this device will still be supported, but without | |
78 | force feedback. | |
79 | ||
80 | config USB_HIDDEV | |
81 | bool "/dev/hiddev raw HID device support" | |
82 | depends on USB_HID | |
83 | help | |
84 | Say Y here if you want to support HID devices (from the USB | |
85 | specification standpoint) that aren't strictly user interface | |
86 | devices, like monitor controls and Uninterruptable Power Supplies. | |
87 | ||
88 | This module supports these devices separately using a separate | |
89 | event interface on /dev/usb/hiddevX (char 180:96 to 180:111). | |
90 | ||
91 | If unsure, say Y. | |
92 | ||
93 | menu "USB HID Boot Protocol drivers" | |
94 | depends on USB!=n && USB_HID!=y | |
95 | ||
96 | config USB_KBD | |
97 | tristate "USB HIDBP Keyboard (simple Boot) support" | |
98 | depends on USB && INPUT | |
99 | ---help--- | |
100 | Say Y here only if you are absolutely sure that you don't want | |
101 | to use the generic HID driver for your USB keyboard and prefer | |
102 | to use the keyboard in its limited Boot Protocol mode instead. | |
103 | ||
104 | This is almost certainly not what you want. This is mostly | |
105 | useful for embedded applications or simple keyboards. | |
106 | ||
107 | To compile this driver as a module, choose M here: the | |
108 | module will be called usbkbd. | |
109 | ||
110 | If even remotely unsure, say N. | |
111 | ||
112 | config USB_MOUSE | |
113 | tristate "USB HIDBP Mouse (simple Boot) support" | |
114 | depends on USB && INPUT | |
115 | ---help--- | |
116 | Say Y here only if you are absolutely sure that you don't want | |
117 | to use the generic HID driver for your USB mouse and prefer | |
118 | to use the mouse in its limited Boot Protocol mode instead. | |
119 | ||
120 | This is almost certainly not what you want. This is mostly | |
121 | useful for embedded applications or simple mice. | |
122 | ||
123 | To compile this driver as a module, choose M here: the | |
124 | module will be called usbmouse. | |
125 | ||
126 | If even remotely unsure, say N. | |
127 | ||
128 | endmenu | |
129 | ||
130 | config USB_AIPTEK | |
131 | tristate "Aiptek 6000U/8000U tablet support" | |
132 | depends on USB && INPUT | |
133 | help | |
134 | Say Y here if you want to use the USB version of the Aiptek 6000U | |
135 | or Aiptek 8000U tablet. Make sure to say Y to "Mouse support" | |
136 | (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" | |
137 | (CONFIG_INPUT_EVDEV) as well. | |
138 | ||
139 | To compile this driver as a module, choose M here: the | |
140 | module will be called aiptek. | |
141 | ||
142 | config USB_WACOM | |
143 | tristate "Wacom Intuos/Graphire tablet support" | |
144 | depends on USB && INPUT | |
145 | help | |
146 | Say Y here if you want to use the USB version of the Wacom Intuos | |
147 | or Graphire tablet. Make sure to say Y to "Mouse support" | |
148 | (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" | |
149 | (CONFIG_INPUT_EVDEV) as well. | |
150 | ||
151 | To compile this driver as a module, choose M here: the | |
152 | module will be called wacom. | |
153 | ||
53880546 SV |
154 | config USB_ACECAD |
155 | tristate "Acecad Flair tablet support" | |
156 | depends on USB && INPUT | |
157 | help | |
158 | Say Y here if you want to use the USB version of the Acecad Flair | |
159 | tablet. Make sure to say Y to "Mouse support" | |
160 | (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" | |
161 | (CONFIG_INPUT_EVDEV) as well. | |
162 | ||
163 | To compile this driver as a module, choose M here: the | |
164 | module will be called acecad. | |
165 | ||
1da177e4 LT |
166 | config USB_KBTAB |
167 | tristate "KB Gear JamStudio tablet support" | |
168 | depends on USB && INPUT | |
169 | help | |
170 | Say Y here if you want to use the USB version of the KB Gear | |
171 | JamStudio tablet. Make sure to say Y to "Mouse support" | |
172 | (CONFIG_INPUT_MOUSEDEV) and/or "Event interface support" | |
173 | (CONFIG_INPUT_EVDEV) as well. | |
174 | ||
175 | To compile this driver as a module, choose M here: the | |
176 | module will be called kbtab. | |
177 | ||
178 | config USB_POWERMATE | |
179 | tristate "Griffin PowerMate and Contour Jog support" | |
180 | depends on USB && INPUT | |
181 | ---help--- | |
182 | Say Y here if you want to use Griffin PowerMate or Contour Jog devices. | |
183 | These are aluminum dials which can measure clockwise and anticlockwise | |
184 | rotation. The dial also acts as a pushbutton. The base contains an LED | |
185 | which can be instructed to pulse or to switch to a particular intensity. | |
186 | ||
187 | You can download userspace tools from | |
188 | <http://sowerbutts.com/powermate/>. | |
189 | ||
190 | To compile this driver as a module, choose M here: the | |
191 | module will be called powermate. | |
192 | ||
193 | config USB_MTOUCH | |
194 | tristate "MicroTouch USB Touchscreen Driver" | |
195 | depends on USB && INPUT | |
196 | ---help--- | |
197 | Say Y here if you want to use a MicroTouch (Now 3M) USB | |
198 | Touchscreen controller. | |
199 | ||
200 | See <file:Documentation/usb/mtouch.txt> for additional information. | |
201 | ||
202 | To compile this driver as a module, choose M here: the | |
203 | module will be called mtouchusb. | |
204 | ||
86084712 HCE |
205 | config USB_ITMTOUCH |
206 | tristate "ITM Touch USB Touchscreen Driver" | |
207 | depends on USB && INPUT | |
208 | ---help--- | |
209 | Say Y here if you want to use a ITM Touch USB | |
210 | Touchscreen controller. | |
211 | ||
212 | This touchscreen is used in LG 1510SF monitors. | |
213 | ||
214 | To compile this driver as a module, choose M here: the | |
215 | module will be called itmtouch. | |
216 | ||
1da177e4 LT |
217 | config USB_EGALAX |
218 | tristate "eGalax TouchKit USB Touchscreen Driver" | |
219 | depends on USB && INPUT | |
220 | ---help--- | |
221 | Say Y here if you want to use a eGalax TouchKit USB | |
222 | Touchscreen controller. | |
223 | ||
224 | The driver has been tested on a Xenarc 700TSV monitor | |
225 | with eGalax touchscreen. | |
226 | ||
227 | Have a look at <http://linux.chapter7.ch/touchkit/> for | |
228 | a usage description and the required user-space stuff. | |
229 | ||
230 | To compile this driver as a module, choose M here: the | |
231 | module will be called touchkitusb. | |
232 | ||
233 | config USB_XPAD | |
234 | tristate "X-Box gamepad support" | |
235 | depends on USB && INPUT | |
236 | ---help--- | |
237 | Say Y here if you want to use the X-Box pad with your computer. | |
238 | Make sure to say Y to "Joystick support" (CONFIG_INPUT_JOYDEV) | |
239 | and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well. | |
240 | ||
241 | For information about how to connect the X-Box pad to USB, see | |
242 | <file:Documentation/input/xpad.txt>. | |
243 | ||
244 | To compile this driver as a module, choose M here: the | |
245 | module will be called xpad. | |
246 | ||
247 | config USB_ATI_REMOTE | |
248 | tristate "ATI / X10 USB RF remote control" | |
249 | depends on USB && INPUT | |
250 | ---help--- | |
251 | Say Y here if you want to use an ATI or X10 "Lola" USB remote control. | |
252 | These are RF remotes with USB receivers. | |
253 | The ATI remote comes with many of ATI's All-In-Wonder video cards. | |
254 | The X10 "Lola" remote is available at: | |
255 | <http://www.x10.com/products/lola_sg1.htm> | |
256 | This driver provides mouse pointer, left and right mouse buttons, | |
257 | and maps all the other remote buttons to keypress events. | |
258 | ||
259 | To compile this driver as a module, choose M here: the module will be | |
260 | called ati_remote. | |
261 | ||
99f83c9c MD |
262 | config USB_KEYSPAN_REMOTE |
263 | tristate "Keyspan DMR USB remote control (EXPERIMENTAL)" | |
264 | depends on USB && INPUT && EXPERIMENTAL | |
265 | ---help--- | |
266 | Say Y here if you want to use a Keyspan DMR USB remote control. | |
267 | Currently only the UIA-11 type of receiver has been tested. The tag | |
268 | on the receiver that connects to the USB port should have a P/N that | |
269 | will tell you what type of DMR you have. The UIA-10 type is not | |
270 | supported at this time. This driver maps all buttons to keypress | |
271 | events. | |
272 | ||
273 | To compile this driver as a module, choose M here: the module will | |
274 | be called keyspan_remote. |