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 iBook/PowerBook/MacBook/MacBookPro special keys"
32 Say Y here if you want support for the special keys (Fn, Numlock) on
33 Apple iBooks, PowerBooks, MacBooks and MacBook Pros.
38 bool "Force feedback support (EXPERIMENTAL)"
39 depends on USB_HID && EXPERIMENTAL
41 Say Y here is you want force feedback support for a few HID devices.
42 See below for a list of supported devices.
44 See <file:Documentation/input/ff.txt> for a description of the force
50 bool "PID device support"
53 Say Y here if you have a PID-compliant device and wish to enable force
54 feedback for it. Microsoft Sidewinder Force Feedback 2 is one of such
58 bool "Logitech devices support"
60 select INPUT_FF_MEMLESS if USB_HID
62 Say Y here if you have one of these devices:
63 - Logitech WingMan Cordless RumblePad
64 - Logitech WingMan Cordless RumblePad 2
65 - Logitech WingMan Force 3D
66 - Logitech Formula Force EX
67 - Logitech MOMO Force wheel
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
74 bool "PantherLord/GreenAsia based device support"
76 select INPUT_FF_MEMLESS if USB_HID
78 Say Y here if you have a PantherLord/GreenAsia based game controller
79 or adapter and want to enable force feedback support for it.
81 config THRUSTMASTER_FF
82 bool "ThrustMaster devices support (EXPERIMENTAL)"
83 depends on HID_FF && EXPERIMENTAL
84 select INPUT_FF_MEMLESS if USB_HID
86 Say Y here if you have a THRUSTMASTER FireStore Dual Power 2 or
87 a THRUSTMASTER Ferrari GT Rumble Force or Force Feedback Wheel,
88 and want to enable force feedback support for it.
89 Note: if you say N here, this device will still be supported, but without
93 bool "Zeroplus based game controller support"
95 select INPUT_FF_MEMLESS if USB_HID
97 Say Y here if you have a Zeroplus based game controller and want to
98 enable force feedback for it.
101 bool "/dev/hiddev raw HID device support"
104 Say Y here if you want to support HID devices (from the USB
105 specification standpoint) that aren't strictly user interface
106 devices, like monitor controls and Uninterruptable Power Supplies.
108 This module supports these devices separately using a separate
109 event interface on /dev/usb/hiddevX (char 180:96 to 180:111).
113 menu "USB HID Boot Protocol drivers"
114 depends on USB!=n && USB_HID!=y
117 tristate "USB HIDBP Keyboard (simple Boot) support"
118 depends on USB && INPUT
120 Say Y here only if you are absolutely sure that you don't want
121 to use the generic HID driver for your USB keyboard and prefer
122 to use the keyboard in its limited Boot Protocol mode instead.
124 This is almost certainly not what you want. This is mostly
125 useful for embedded applications or simple keyboards.
127 To compile this driver as a module, choose M here: the
128 module will be called usbkbd.
130 If even remotely unsure, say N.
133 tristate "USB HIDBP Mouse (simple Boot) support"
134 depends on USB && INPUT
136 Say Y here only if you are absolutely sure that you don't want
137 to use the generic HID driver for your USB mouse and prefer
138 to use the mouse in its limited Boot Protocol mode instead.
140 This is almost certainly not what you want. This is mostly
141 useful for embedded applications or simple mice.
143 To compile this driver as a module, choose M here: the
144 module will be called usbmouse.
146 If even remotely unsure, say N.