Version:  2.0.40 2.2.26 2.4.37 2.6.39 3.0 3.1 3.2 3.3 3.4 3.5 3.6 3.7 3.8 3.9 3.10 3.11 3.12 3.13 3.14 3.15

Linux/drivers/input/joystick/Kconfig

  1 #
  2 # Joystick driver configuration
  3 #
  4 menuconfig INPUT_JOYSTICK
  5         bool "Joysticks/Gamepads"
  6         help
  7           If you have a joystick, 6dof controller, gamepad, steering wheel,
  8           weapon control system or something like that you can say Y here
  9           and the list of supported devices will be displayed. This option
 10           doesn't affect the kernel.
 11 
 12           Please read the file <file:Documentation/input/joystick.txt> which
 13           contains more information.
 14 
 15 if INPUT_JOYSTICK
 16 
 17 config JOYSTICK_ANALOG
 18         tristate "Classic PC analog joysticks and gamepads"
 19         select GAMEPORT
 20         ---help---
 21           Say Y here if you have a joystick that connects to the PC
 22           gameport. In addition to the usual PC analog joystick, this driver
 23           supports many extensions, including joysticks with throttle control,
 24           with rudders, additional hats and buttons compatible with CH
 25           Flightstick Pro, ThrustMaster FCS, 6 and 8 button gamepads, or
 26           Saitek Cyborg joysticks.
 27 
 28           Please read the file <file:Documentation/input/joystick.txt> which
 29           contains more information.
 30 
 31           To compile this driver as a module, choose M here: the
 32           module will be called analog.
 33 
 34 config JOYSTICK_A3D
 35         tristate "Assassin 3D and MadCatz Panther devices"
 36         select GAMEPORT
 37         help
 38           Say Y here if you have an FPGaming or MadCatz controller using the
 39           A3D protocol over the PC gameport.
 40 
 41           To compile this driver as a module, choose M here: the
 42           module will be called a3d.
 43 
 44 config JOYSTICK_ADI
 45         tristate "Logitech ADI digital joysticks and gamepads"
 46         select GAMEPORT
 47         help
 48           Say Y here if you have a Logitech controller using the ADI
 49           protocol over the PC gameport.
 50 
 51           To compile this driver as a module, choose M here: the
 52           module will be called adi.
 53 
 54 config JOYSTICK_COBRA
 55         tristate "Creative Labs Blaster Cobra gamepad"
 56         select GAMEPORT
 57         help
 58           Say Y here if you have a Creative Labs Blaster Cobra gamepad.
 59 
 60           To compile this driver as a module, choose M here: the
 61           module will be called cobra.
 62 
 63 config JOYSTICK_GF2K
 64         tristate "Genius Flight2000 Digital joysticks and gamepads"
 65         select GAMEPORT
 66         help
 67           Say Y here if you have a Genius Flight2000 or MaxFighter digitally
 68           communicating joystick or gamepad.
 69 
 70           To compile this driver as a module, choose M here: the
 71           module will be called gf2k.
 72 
 73 config JOYSTICK_GRIP
 74         tristate "Gravis GrIP joysticks and gamepads"
 75         select GAMEPORT
 76         help
 77           Say Y here if you have a Gravis controller using the GrIP protocol
 78           over the PC gameport.
 79 
 80           To compile this driver as a module, choose M here: the
 81           module will be called grip.
 82 
 83 config JOYSTICK_GRIP_MP
 84         tristate "Gravis GrIP MultiPort"
 85         select GAMEPORT
 86         help
 87           Say Y here if you have the original Gravis GrIP MultiPort, a hub
 88           that connects to the gameport and you connect gamepads to it.
 89 
 90           To compile this driver as a module, choose M here: the
 91           module will be called grip_mp.
 92 
 93 config JOYSTICK_GUILLEMOT
 94         tristate "Guillemot joysticks and gamepads"
 95         select GAMEPORT
 96         help
 97           Say Y here if you have a Guillemot joystick using a digital
 98           protocol over the PC gameport.
 99 
100           To compile this driver as a module, choose M here: the
101           module will be called guillemot.
102 
103 config JOYSTICK_INTERACT
104         tristate "InterAct digital joysticks and gamepads"
105         select GAMEPORT
106         help
107           Say Y here if you have an InterAct gameport or joystick
108           communicating digitally over the gameport.
109 
110           To compile this driver as a module, choose M here: the
111           module will be called interact.
112 
113 config JOYSTICK_SIDEWINDER
114         tristate "Microsoft SideWinder digital joysticks and gamepads"
115         select GAMEPORT
116         help
117           Say Y here if you have a Microsoft controller using the Digital
118           Overdrive protocol over PC gameport.
119 
120           To compile this driver as a module, choose M here: the
121           module will be called sidewinder.
122 
123 config JOYSTICK_TMDC
124         tristate "ThrustMaster DirectConnect joysticks and gamepads"
125         select GAMEPORT
126         help
127           Say Y here if you have a ThrustMaster controller using the
128           DirectConnect (BSP) protocol over the PC gameport.
129 
130           To compile this driver as a module, choose M here: the
131           module will be called tmdc.
132 
133 source "drivers/input/joystick/iforce/Kconfig"
134 
135 config JOYSTICK_WARRIOR
136         tristate "Logitech WingMan Warrior joystick"
137         select SERIO
138         help
139           Say Y here if you have a Logitech WingMan Warrior joystick connected
140           to your computer's serial port.
141 
142           To compile this driver as a module, choose M here: the
143           module will be called warrior.
144 
145 config JOYSTICK_MAGELLAN
146         tristate "LogiCad3d Magellan/SpaceMouse 6dof controllers"
147         select SERIO
148         help
149           Say Y here if you have a Magellan or Space Mouse 6DOF controller
150           connected to your computer's serial port.
151 
152           To compile this driver as a module, choose M here: the
153           module will be called magellan.
154 
155 config JOYSTICK_SPACEORB
156         tristate "SpaceTec SpaceOrb/Avenger 6dof controllers"
157         select SERIO
158         help
159           Say Y here if you have a SpaceOrb 360 or SpaceBall Avenger 6DOF
160           controller connected to your computer's serial port.
161 
162           To compile this driver as a module, choose M here: the
163           module will be called spaceorb.
164 
165 config JOYSTICK_SPACEBALL
166         tristate "SpaceTec SpaceBall 6dof controllers"
167         select SERIO
168         help
169           Say Y here if you have a SpaceTec SpaceBall 2003/3003/4000 FLX
170           controller connected to your computer's serial port. For the
171           SpaceBall 4000 USB model, use the USB HID driver.
172 
173           To compile this driver as a module, choose M here: the
174           module will be called spaceball.
175 
176 config JOYSTICK_STINGER
177         tristate "Gravis Stinger gamepad"
178         select SERIO
179         help
180           Say Y here if you have a Gravis Stinger connected to one of your
181           serial ports.
182 
183           To compile this driver as a module, choose M here: the
184           module will be called stinger.
185 
186 config JOYSTICK_TWIDJOY
187         tristate "Twiddler as a joystick"
188         select SERIO
189         help
190           Say Y here if you have a Handykey Twiddler connected to your
191           computer's serial port and want to use it as a joystick.
192 
193           To compile this driver as a module, choose M here: the
194           module will be called twidjoy.
195 
196 config JOYSTICK_ZHENHUA
197         tristate "5-byte Zhenhua RC transmitter"
198         select SERIO
199         help
200           Say Y here if you have a Zhen Hua PPM-4CH transmitter which is
201           supplied with a ready to fly micro electric indoor helicopters
202           such as EasyCopter, Lama, MiniCopter, DragonFly or Jabo and want
203           to use it via serial cable as a joystick.
204 
205           To compile this driver as a module, choose M here: the
206           module will be called zhenhua.
207 
208 config JOYSTICK_DB9
209         tristate "Multisystem, Sega Genesis, Saturn joysticks and gamepads"
210         depends on PARPORT
211         help
212           Say Y here if you have a Sega Master System gamepad, Sega Genesis
213           gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
214           Commodore, Amstrad CPC joystick connected to your parallel port.
215           For more information on how to use the driver please read
216           <file:Documentation/input/joystick-parport.txt>.
217 
218           To compile this driver as a module, choose M here: the
219           module will be called db9.
220 
221 config JOYSTICK_GAMECON
222         tristate "Multisystem, NES, SNES, N64, PSX joysticks and gamepads"
223         depends on PARPORT
224         select INPUT_FF_MEMLESS
225         ---help---
226           Say Y here if you have a Nintendo Entertainment System gamepad,
227           Super Nintendo Entertainment System gamepad, Nintendo 64 gamepad,
228           Sony PlayStation gamepad or a Multisystem -- Atari, Amiga,
229           Commodore, Amstrad CPC joystick connected to your parallel port.
230           For more information on how to use the driver please read
231           <file:Documentation/input/joystick-parport.txt>.
232 
233           To compile this driver as a module, choose M here: the
234           module will be called gamecon.
235 
236 config JOYSTICK_TURBOGRAFX
237         tristate "Multisystem joysticks via TurboGraFX device"
238         depends on PARPORT
239         help
240           Say Y here if you have the TurboGraFX interface by Steffen Schwenke,
241           and want to use it with Multisystem -- Atari, Amiga, Commodore,
242           Amstrad CPC joystick. For more information on how to use the driver
243           please read <file:Documentation/input/joystick-parport.txt>.
244 
245           To compile this driver as a module, choose M here: the
246           module will be called turbografx.
247 
248 config JOYSTICK_AMIGA
249         tristate "Amiga joysticks"
250         depends on AMIGA
251         help
252           Say Y here if you have an Amiga with a digital joystick connected
253           to it.
254 
255           To compile this driver as a module, choose M here: the
256           module will be called amijoy.
257 
258 config JOYSTICK_AS5011
259         tristate "Austria Microsystem AS5011 joystick"
260         depends on I2C
261         help
262           Say Y here if you have an AS5011 digital joystick connected to your
263           system.
264 
265           To compile this driver as a module, choose M here: the
266           module will be called as5011.
267 
268 config JOYSTICK_JOYDUMP
269         tristate "Gameport data dumper"
270         select GAMEPORT
271         help
272           Say Y here if you want to dump data from your joystick into the system
273           log for debugging purposes. Say N if you are making a production
274           configuration or aren't sure.
275 
276           To compile this driver as a module, choose M here: the
277           module will be called joydump.
278 
279 config JOYSTICK_XPAD
280         tristate "X-Box gamepad support"
281         depends on USB_ARCH_HAS_HCD
282         select USB
283         help
284           Say Y here if you want to use the X-Box pad with your computer.
285           Make sure to say Y to "Joystick support" (CONFIG_INPUT_JOYDEV)
286           and/or "Event interface support" (CONFIG_INPUT_EVDEV) as well.
287 
288           For information about how to connect the X-Box pad to USB, see
289           <file:Documentation/input/xpad.txt>.
290 
291           To compile this driver as a module, choose M here: the
292           module will be called xpad.
293 
294 config JOYSTICK_XPAD_FF
295         bool "X-Box gamepad rumble support"
296         depends on JOYSTICK_XPAD && INPUT
297         select INPUT_FF_MEMLESS
298         ---help---
299           Say Y here if you want to take advantage of xbox 360 rumble features.
300 
301 config JOYSTICK_XPAD_LEDS
302         bool "LED Support for Xbox360 controller 'BigX' LED"
303         depends on JOYSTICK_XPAD && (LEDS_CLASS=y || LEDS_CLASS=JOYSTICK_XPAD)
304         ---help---
305           This option enables support for the LED which surrounds the Big X on
306           XBox 360 controller.
307 
308 config JOYSTICK_WALKERA0701
309         tristate "Walkera WK-0701 RC transmitter"
310         depends on HIGH_RES_TIMERS && PARPORT
311         help
312           Say Y or M here if you have a Walkera WK-0701 transmitter which is
313           supplied with a ready to fly Walkera helicopters such as HM36,
314           HM37, HM60 and want to use it via parport as a joystick. More
315           information is available: <file:Documentation/input/walkera0701.txt>
316 
317           To compile this driver as a module, choose M here: the
318           module will be called walkera0701.
319 
320 config JOYSTICK_MAPLE
321         tristate "Dreamcast control pad"
322         depends on MAPLE
323         help
324           Say Y here if you have a SEGA Dreamcast and want to use your
325           controller as a joystick.
326 
327           Most Dreamcast users will say Y.
328 
329           To compile this as a module choose M here: the module will be called
330           maplecontrol.
331 
332 endif

This page was automatically generated by LXR 0.3.1 (source).  •  Linux is a registered trademark of Linus Torvalds  •  Contact us