Kconfig 7.9 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256
  1. #
  2. # Joystick driver configuration
  3. #
  4. menuconfig 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. Please read the file <file:Documentation/input/joystick.txt> which
  12. contains more information.
  13. if INPUT_JOYSTICK
  14. config JOYSTICK_ANALOG
  15. tristate "Classic PC analog joysticks and gamepads"
  16. select GAMEPORT
  17. ---help---
  18. Say Y here if you have a joystick that connects to the PC
  19. gameport. In addition to the usual PC analog joystick, this driver
  20. supports many extensions, including joysticks with throttle control,
  21. with rudders, additional hats and buttons compatible with CH
  22. Flightstick Pro, ThrustMaster FCS, 6 and 8 button gamepads, or
  23. Saitek Cyborg joysticks.
  24. Please read the file <file:Documentation/input/joystick.txt> which
  25. contains more information.
  26. To compile this driver as a module, choose M here: the
  27. module will be called analog.
  28. config JOYSTICK_A3D
  29. tristate "Assassin 3D and MadCatz Panther devices"
  30. select GAMEPORT
  31. help
  32. Say Y here if you have an FPGaming or MadCatz controller using the
  33. A3D protocol over the PC gameport.
  34. To compile this driver as a module, choose M here: the
  35. module will be called a3d.
  36. config JOYSTICK_ADI
  37. tristate "Logitech ADI digital joysticks and gamepads"
  38. select GAMEPORT
  39. help
  40. Say Y here if you have a Logitech controller using the ADI
  41. protocol over the PC gameport.
  42. To compile this driver as a module, choose M here: the
  43. module will be called adi.
  44. config JOYSTICK_COBRA
  45. tristate "Creative Labs Blaster Cobra gamepad"
  46. select GAMEPORT
  47. help
  48. Say Y here if you have a Creative Labs Blaster Cobra gamepad.
  49. To compile this driver as a module, choose M here: the
  50. module will be called cobra.
  51. config JOYSTICK_GF2K
  52. tristate "Genius Flight2000 Digital joysticks and gamepads"
  53. select GAMEPORT
  54. help
  55. Say Y here if you have a Genius Flight2000 or MaxFighter digitally
  56. communicating joystick or gamepad.
  57. To compile this driver as a module, choose M here: the
  58. module will be called gf2k.
  59. config JOYSTICK_GRIP
  60. tristate "Gravis GrIP joysticks and gamepads"
  61. select GAMEPORT
  62. help
  63. Say Y here if you have a Gravis controller using the GrIP protocol
  64. over the PC gameport.
  65. To compile this driver as a module, choose M here: the
  66. module will be called grip.
  67. config JOYSTICK_GRIP_MP
  68. tristate "Gravis GrIP MultiPort"
  69. select GAMEPORT
  70. help
  71. Say Y here if you have the original Gravis GrIP MultiPort, a hub
  72. that connects to the gameport and you connect gamepads to it.
  73. To compile this driver as a module, choose M here: the
  74. module will be called grip_mp.
  75. config JOYSTICK_GUILLEMOT
  76. tristate "Guillemot joysticks and gamepads"
  77. select GAMEPORT
  78. help
  79. Say Y here if you have a Guillemot joystick using a digital
  80. protocol over the PC gameport.
  81. To compile this driver as a module, choose M here: the
  82. module will be called guillemot.
  83. config JOYSTICK_INTERACT
  84. tristate "InterAct digital joysticks and gamepads"
  85. select GAMEPORT
  86. help
  87. Say Y here if you have an InterAct gameport or joystick
  88. communicating digitally over the gameport.
  89. To compile this driver as a module, choose M here: the
  90. module will be called interact.
  91. config JOYSTICK_SIDEWINDER
  92. tristate "Microsoft SideWinder digital joysticks and gamepads"
  93. select GAMEPORT
  94. help
  95. Say Y here if you have a Microsoft controller using the Digital
  96. Overdrive protocol over PC gameport.
  97. To compile this driver as a module, choose M here: the
  98. module will be called sidewinder.
  99. config JOYSTICK_TMDC
  100. tristate "ThrustMaster DirectConnect joysticks and gamepads"
  101. select GAMEPORT
  102. help
  103. Say Y here if you have a ThrustMaster controller using the
  104. DirectConnect (BSP) protocol over the PC gameport.
  105. To compile this driver as a module, choose M here: the
  106. module will be called tmdc.
  107. source "drivers/input/joystick/iforce/Kconfig"
  108. config JOYSTICK_WARRIOR
  109. tristate "Logitech WingMan Warrior joystick"
  110. select SERIO
  111. help
  112. Say Y here if you have a Logitech WingMan Warrior joystick connected
  113. to your computer's serial port.
  114. To compile this driver as a module, choose M here: the
  115. module will be called warrior.
  116. config JOYSTICK_MAGELLAN
  117. tristate "LogiCad3d Magellan/SpaceMouse 6dof controllers"
  118. select SERIO
  119. help
  120. Say Y here if you have a Magellan or Space Mouse 6DOF controller
  121. connected to your computer's serial port.
  122. To compile this driver as a module, choose M here: the
  123. module will be called magellan.
  124. config JOYSTICK_SPACEORB
  125. tristate "SpaceTec SpaceOrb/Avenger 6dof controllers"
  126. select SERIO
  127. help
  128. Say Y here if you have a SpaceOrb 360 or SpaceBall Avenger 6DOF
  129. controller connected to your computer's serial port.
  130. To compile this driver as a module, choose M here: the
  131. module will be called spaceorb.
  132. config JOYSTICK_SPACEBALL
  133. tristate "SpaceTec SpaceBall 6dof controllers"
  134. select SERIO
  135. help
  136. Say Y here if you have a SpaceTec SpaceBall 2003/3003/4000 FLX
  137. controller connected to your computer's serial port. For the
  138. SpaceBall 4000 USB model, use the USB HID driver.
  139. To compile this driver as a module, choose M here: the
  140. module will be called spaceball.
  141. config JOYSTICK_STINGER
  142. tristate "Gravis Stinger gamepad"
  143. select SERIO
  144. help
  145. Say Y here if you have a Gravis Stinger connected to one of your
  146. serial ports.
  147. To compile this driver as a module, choose M here: the
  148. module will be called stinger.
  149. config JOYSTICK_TWIDJOY
  150. tristate "Twiddler as a joystick"
  151. select SERIO
  152. help
  153. Say Y here if you have a Handykey Twiddler connected to your
  154. computer's serial port and want to use it as a joystick.
  155. To compile this driver as a module, choose M here: the
  156. module will be called twidjoy.
  157. config JOYSTICK_DB9
  158. tristate "Multisystem, Sega Genesis, Saturn joysticks and gamepads"
  159. depends on PARPORT
  160. ---help---
  161. Say Y here if you have a Sega Master System gamepad, Sega Genesis
  162. gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
  163. Commodore, Amstrad CPC joystick connected to your parallel port.
  164. For more information on how to use the driver please read
  165. <file:Documentation/input/joystick-parport.txt>.
  166. To compile this driver as a module, choose M here: the
  167. module will be called db9.
  168. config JOYSTICK_GAMECON
  169. tristate "Multisystem, NES, SNES, N64, PSX joysticks and gamepads"
  170. depends on PARPORT
  171. ---help---
  172. Say Y here if you have a Nintendo Entertainment System gamepad,
  173. Super Nintendo Entertainment System gamepad, Nintendo 64 gamepad,
  174. Sony PlayStation gamepad or a Multisystem -- Atari, Amiga,
  175. Commodore, Amstrad CPC joystick connected to your parallel port.
  176. For more information on how to use the driver please read
  177. <file:Documentation/input/joystick-parport.txt>.
  178. To compile this driver as a module, choose M here: the
  179. module will be called gamecon.
  180. config JOYSTICK_TURBOGRAFX
  181. tristate "Multisystem joysticks via TurboGraFX device"
  182. depends on PARPORT
  183. help
  184. Say Y here if you have the TurboGraFX interface by Steffen Schwenke,
  185. and want to use it with Multisystem -- Atari, Amiga, Commodore,
  186. Amstrad CPC joystick. For more information on how to use the driver
  187. please read <file:Documentation/input/joystick-parport.txt>.
  188. To compile this driver as a module, choose M here: the
  189. module will be called turbografx.
  190. config JOYSTICK_AMIGA
  191. tristate "Amiga joysticks"
  192. depends on AMIGA
  193. help
  194. Say Y here if you have an Amiga with a digital joystick connected
  195. to it.
  196. To compile this driver as a module, choose M here: the
  197. module will be called amijoy.
  198. config JOYSTICK_JOYDUMP
  199. tristate "Gameport data dumper"
  200. select GAMEPORT
  201. help
  202. Say Y here if you want to dump data from your joystick into the system
  203. log for debugging purposes. Say N if you are making a production
  204. configuration or aren't sure.
  205. To compile this driver as a module, choose M here: the
  206. module will be called joydump.
  207. endif