xref: /linux/drivers/input/joystick/Kconfig (revision f3d9478b2ce468c3115b02ecae7e975990697f15)
1#
2# Joystick driver configuration
3#
4menuconfig INPUT_JOYSTICK
5	bool "Joysticks"
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
15if INPUT_JOYSTICK
16
17config 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
34config JOYSTICK_A3D
35	tristate "Assasin 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
44config 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
54config 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
63config 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
73config 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
83config 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
93config 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
103config 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
113config 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
123config 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
133source "drivers/input/joystick/iforce/Kconfig"
134
135config 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
145config 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
155config 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
165config 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
176config 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
186config 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
196config JOYSTICK_DB9
197	tristate "Multisystem, Sega Genesis, Saturn joysticks and gamepads"
198	depends on PARPORT
199	---help---
200	  Say Y here if you have a Sega Master System gamepad, Sega Genesis
201	  gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
202	  Commodore, Amstrad CPC joystick connected to your parallel port.
203	  For more information on how to use the driver please read
204	  <file:Documentation/input/joystick-parport.txt>.
205
206	  To compile this driver as a module, choose M here: the
207	  module will be called db9.
208
209config JOYSTICK_GAMECON
210	tristate "Multisystem, NES, SNES, N64, PSX joysticks and gamepads"
211	depends on PARPORT
212	---help---
213	  Say Y here if you have a Nintendo Entertainment System gamepad,
214	  Super Nintendo Entertainment System gamepad, Nintendo 64 gamepad,
215	  Sony PlayStation gamepad or a Multisystem -- Atari, Amiga,
216	  Commodore, Amstrad CPC joystick connected to your parallel port.
217	  For more information on how to use the driver please read
218	  <file:Documentation/input/joystick-parport.txt>.
219
220	  To compile this driver as a module, choose M here: the
221	  module will be called gamecon.
222
223config JOYSTICK_TURBOGRAFX
224	tristate "Multisystem joysticks via TurboGraFX device"
225	depends on PARPORT
226	help
227	  Say Y here if you have the TurboGraFX interface by Steffen Schwenke,
228	  and want to use it with Multisystem -- Atari, Amiga, Commodore,
229	  Amstrad CPC joystick. For more information on how to use the driver
230	  please read <file:Documentation/input/joystick-parport.txt>.
231
232	  To compile this driver as a module, choose M here: the
233	  module will be called turbografx.
234
235config JOYSTICK_AMIGA
236	tristate "Amiga joysticks"
237	depends on AMIGA
238	help
239	  Say Y here if you have an Amiga with a digital joystick connected
240	  to it.
241
242	  To compile this driver as a module, choose M here: the
243	  module will be called amijoy.
244
245config JOYSTICK_JOYDUMP
246	tristate "Gameport data dumper"
247	select GAMEPORT
248	help
249	  Say Y here if you want to dump data from your joystick into the system
250	  log for debugging purposes. Say N if you are making a production
251	  configuration or aren't sure.
252
253	  To compile this driver as a module, choose M here: the
254	  module will be called joydump.
255
256endif
257