2 # Joystick driver configuration
8 If you have a joystick, 6dof controller, gamepad, steering wheel,
9 weapon control system or something like that you can say Y here
10 and the list of supported devices will be displayed. This option
11 doesn't affect the kernel.
13 Please read the file <file:Documentation/input/joystick.txt> which
14 contains more information.
16 config JOYSTICK_ANALOG
17 tristate "Classic PC analog joysticks and gamepads"
18 depends on INPUT && INPUT_JOYSTICK && GAMEPORT
20 Say Y here if you have a joystick that connects to the PC
21 gameport. In addition to the usual PC analog joystick, this driver
22 supports many extensions, including joysticks with throttle control,
23 with rudders, additional hats and buttons compatible with CH
24 Flightstick Pro, ThrustMaster FCS, 6 and 8 button gamepads, or
25 Saitek Cyborg joysticks.
27 Please read the file <file:Documentation/input/joystick.txt> which
28 contains more information.
30 To compile this driver as a module, choose M here: the
31 module will be called analog.
34 tristate "Assasin 3D and MadCatz Panther devices"
35 depends on INPUT && INPUT_JOYSTICK && GAMEPORT
37 Say Y here if you have an FPGaming or MadCatz controller using the
38 A3D protocol over the PC gameport.
40 To compile this driver as a module, choose M here: the
41 module will be called a3d.
44 tristate "Logitech ADI digital joysticks and gamepads"
45 depends on INPUT && INPUT_JOYSTICK && GAMEPORT
47 Say Y here if you have a Logitech controller using the ADI
48 protocol over the PC gameport.
50 To compile this driver as a module, choose M here: the
51 module will be called adi.
54 tristate "Creative Labs Blaster Cobra gamepad"
55 depends on INPUT && INPUT_JOYSTICK && GAMEPORT
57 Say Y here if you have a Creative Labs Blaster Cobra gamepad.
59 To compile this driver as a module, choose M here: the
60 module will be called cobra.
63 tristate "Genius Flight2000 Digital joysticks and gamepads"
64 depends on INPUT && INPUT_JOYSTICK && GAMEPORT
66 Say Y here if you have a Genius Flight2000 or MaxFighter digitally
67 communicating joystick or gamepad.
69 To compile this driver as a module, choose M here: the
70 module will be called gf2k.
73 tristate "Gravis GrIP joysticks and gamepads"
74 depends on INPUT && INPUT_JOYSTICK && GAMEPORT
76 Say Y here if you have a Gravis controller using the GrIP protocol
79 To compile this driver as a module, choose M here: the
80 module will be called grip.
82 config JOYSTICK_GRIP_MP
83 tristate "Gravis GrIP MultiPort"
84 depends on INPUT && INPUT_JOYSTICK && GAMEPORT
86 Say Y here if you have the original Gravis GrIP MultiPort, a hub
87 that connects to the gameport and you connect gamepads to it.
89 To compile this driver as a module, choose M here: the
90 module will be called grip_mp.
92 config JOYSTICK_GUILLEMOT
93 tristate "Guillemot joysticks and gamepads"
94 depends on INPUT && INPUT_JOYSTICK && GAMEPORT
96 Say Y here if you have a Guillemot joystick using a digital
97 protocol over the PC gameport.
99 To compile this driver as a module, choose M here: the
100 module will be called guillemot.
102 config JOYSTICK_INTERACT
103 tristate "InterAct digital joysticks and gamepads"
104 depends on INPUT && INPUT_JOYSTICK && GAMEPORT
106 Say Y here if you have an InterAct gameport or joystick
107 communicating digitally over the gameport.
109 To compile this driver as a module, choose M here: the
110 module will be called interact.
112 config JOYSTICK_SIDEWINDER
113 tristate "Microsoft SideWinder digital joysticks and gamepads"
114 depends on INPUT && INPUT_JOYSTICK && GAMEPORT
116 Say Y here if you have a Microsoft controller using the Digital
117 Overdrive protocol over PC gameport.
119 To compile this driver as a module, choose M here: the
120 module will be called sidewinder.
123 tristate "ThrustMaster DirectConnect joysticks and gamepads"
124 depends on INPUT && INPUT_JOYSTICK && GAMEPORT
126 Say Y here if you have a ThrustMaster controller using the
127 DirectConnect (BSP) protocol over the PC gameport.
129 To compile this driver as a module, choose M here: the
130 module will be called tmdc.
132 source "drivers/input/joystick/iforce/Kconfig"
134 config JOYSTICK_WARRIOR
135 tristate "Logitech WingMan Warrior joystick"
136 depends on INPUT && INPUT_JOYSTICK
139 Say Y here if you have a Logitech WingMan Warrior joystick connected
140 to your computer's serial port.
142 To compile this driver as a module, choose M here: the
143 module will be called warrior.
145 config JOYSTICK_MAGELLAN
146 tristate "LogiCad3d Magellan/SpaceMouse 6dof controllers"
147 depends on INPUT && INPUT_JOYSTICK
150 Say Y here if you have a Magellan or Space Mouse 6DOF controller
151 connected to your computer's serial port.
153 To compile this driver as a module, choose M here: the
154 module will be called magellan.
156 config JOYSTICK_SPACEORB
157 tristate "SpaceTec SpaceOrb/Avenger 6dof controllers"
158 depends on INPUT && INPUT_JOYSTICK
161 Say Y here if you have a SpaceOrb 360 or SpaceBall Avenger 6DOF
162 controller connected to your computer's serial port.
164 To compile this driver as a module, choose M here: the
165 module will be called spaceorb.
167 config JOYSTICK_SPACEBALL
168 tristate "SpaceTec SpaceBall 6dof controllers"
169 depends on INPUT && INPUT_JOYSTICK
172 Say Y here if you have a SpaceTec SpaceBall 2003/3003/4000 FLX
173 controller connected to your computer's serial port. For the
174 SpaceBall 4000 USB model, use the USB HID driver.
176 To compile this driver as a module, choose M here: the
177 module will be called spaceball.
179 config JOYSTICK_STINGER
180 tristate "Gravis Stinger gamepad"
181 depends on INPUT && INPUT_JOYSTICK
184 Say Y here if you have a Gravis Stinger connected to one of your
187 To compile this driver as a module, choose M here: the
188 module will be called stinger.
190 config JOYSTICK_TWIDDLER
191 tristate "Twiddler as a joystick"
192 depends on INPUT && INPUT_JOYSTICK
195 Say Y here if you have a Handykey Twiddler connected to your
196 computer's serial port and want to use it as a joystick.
198 To compile this driver as a module, choose M here: the
199 module will be called twidjoy.
202 tristate "Multisystem, Sega Genesis, Saturn joysticks and gamepads"
203 depends on INPUT && INPUT_JOYSTICK && PARPORT
205 Say Y here if you have a Sega Master System gamepad, Sega Genesis
206 gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
207 Commodore, Amstrad CPC joystick connected to your parallel port.
208 For more information on how to use the driver please read
209 <file:Documentation/input/joystick-parport.txt>.
211 To compile this driver as a module, choose M here: the
212 module will be called db9.
214 config JOYSTICK_GAMECON
215 tristate "Multisystem, NES, SNES, N64, PSX joysticks and gamepads"
216 depends on INPUT && INPUT_JOYSTICK && PARPORT
218 Say Y here if you have a Nintendo Entertainment System gamepad,
219 Super Nintendo Entertainment System gamepad, Nintendo 64 gamepad,
220 Sony PlayStation gamepad or a Multisystem -- Atari, Amiga,
221 Commodore, Amstrad CPC joystick connected to your parallel port.
222 For more information on how to use the driver please read
223 <file:Documentation/input/joystick-parport.txt>.
225 To compile this driver as a module, choose M here: the
226 module will be called gamecon.
228 config JOYSTICK_TURBOGRAFX
229 tristate "Multisystem joysticks via TurboGraFX device"
230 depends on INPUT && INPUT_JOYSTICK && PARPORT
232 Say Y here if you have the TurboGraFX interface by Steffen Schwenke,
233 and want to use it with Multisystem -- Atari, Amiga, Commodore,
234 Amstrad CPC joystick. For more information on how to use the driver
235 please read <file:Documentation/input/joystick-parport.txt>.
237 To compile this driver as a module, choose M here: the
238 module will be called turbografx.
240 config JOYSTICK_AMIGA
241 tristate "Amiga joysticks"
242 depends on AMIGA && INPUT && INPUT_JOYSTICK
244 Say Y here if you have an Amiga with a digital joystick connected
247 To compile this driver as a module, choose M here: the
248 module will be called amijoy.
250 config JOYSTICK_JOYDUMP
251 tristate "Gameport data dumper"
252 depends on INPUT && INPUT_JOYSTICK && GAMEPORT
254 Say Y here if you want to dump data from your joystick into the system
255 log for debugging purposes. Say N if you are making a production
256 configuration or aren't sure.
258 To compile this driver as a module, choose M here: the
259 module will be called joydump.