1 comment "USB Input Devices"
5 tristate "USB Human Interface Device (full HID) support"
7 depends on USB && INPUT
10 Say Y here if you want full HID support to connect USB keyboards,
11 mice, joysticks, graphic tablets, or any other HID based devices
12 to your computer via USB, as well as Uninterruptible Power Supply
13 (UPS) and monitor control devices.
15 You can't use this driver and the HIDBP (Boot Protocol) keyboard
16 and mouse drivers at the same time. More information is available:
17 <file:Documentation/input/input.txt>.
21 To compile this driver as a module, choose M here: the
22 module will be called usbhid.
24 comment "Input core support is needed for USB HID input layer or HIDBP support"
25 depends on USB_HID && INPUT=n
27 config USB_HIDINPUT_POWERBOOK
28 bool "Enable support for Apple laptop/aluminum USB special keys"
32 Say Y here if you want support for the special keys (Fn, Numlock) on
33 Apple iBooks, PowerBooks, MacBooks, MacBook Pros and aluminum USB
39 bool "Force feedback support (EXPERIMENTAL)"
40 depends on USB_HID && EXPERIMENTAL
42 Say Y here is you want force feedback support for a few HID devices.
43 See below for a list of supported devices.
45 See <file:Documentation/input/ff.txt> for a description of the force
51 bool "PID device support"
54 Say Y here if you have a PID-compliant device and wish to enable force
55 feedback for it. Microsoft Sidewinder Force Feedback 2 is one of such
59 bool "Logitech devices support"
61 select INPUT_FF_MEMLESS if USB_HID
63 Say Y here if you have one of these devices:
64 - Logitech WingMan Cordless RumblePad
65 - Logitech WingMan Cordless RumblePad 2
66 - Logitech WingMan Force 3D
67 - Logitech Formula Force EX
68 - Logitech MOMO Force wheel
70 and if you want to enable force feedback for them.
71 Note: if you say N here, this device will still be supported, but without
75 bool "PantherLord/GreenAsia based device support"
77 select INPUT_FF_MEMLESS if USB_HID
79 Say Y here if you have a PantherLord/GreenAsia based game controller
80 or adapter and want to enable force feedback support for it.
82 config THRUSTMASTER_FF
83 bool "ThrustMaster devices support (EXPERIMENTAL)"
84 depends on HID_FF && EXPERIMENTAL
85 select INPUT_FF_MEMLESS if USB_HID
87 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
88 a THRUSTMASTER Ferrari GT Rumble Force or Force Feedback Wheel,
89 and want to enable force feedback support for it.
90 Note: if you say N here, this device will still be supported, but without
94 bool "Zeroplus based game controller support"
96 select INPUT_FF_MEMLESS if USB_HID
98 Say Y here if you have a Zeroplus based game controller and want to
99 enable force feedback for it.
102 bool "/dev/hiddev raw HID device support"
105 Say Y here if you want to support HID devices (from the USB
106 specification standpoint) that aren't strictly user interface
107 devices, like monitor controls and Uninterruptable Power Supplies.
109 This module supports these devices separately using a separate
110 event interface on /dev/usb/hiddevX (char 180:96 to 180:111).
114 menu "USB HID Boot Protocol drivers"
115 depends on USB!=n && USB_HID!=y
118 tristate "USB HIDBP Keyboard (simple Boot) support"
119 depends on USB && INPUT
121 Say Y here only if you are absolutely sure that you don't want
122 to use the generic HID driver for your USB keyboard and prefer
123 to use the keyboard in its limited Boot Protocol mode instead.
125 This is almost certainly not what you want. This is mostly
126 useful for embedded applications or simple keyboards.
128 To compile this driver as a module, choose M here: the
129 module will be called usbkbd.
131 If even remotely unsure, say N.
134 tristate "USB HIDBP Mouse (simple Boot) support"
135 depends on USB && INPUT
137 Say Y here only if you are absolutely sure that you don't want
138 to use the generic HID driver for your USB mouse and prefer
139 to use the mouse in its limited Boot Protocol mode instead.
141 This is almost certainly not what you want. This is mostly
142 useful for embedded applications or simple mice.
144 To compile this driver as a module, choose M here: the
145 module will be called usbmouse.
147 If even remotely unsure, say N.