Lines Matching +full:on +full:- +full:the +full:- +full:fly
1 # SPDX-License-Identifier: GPL-2.0-only
7 depends on !UML
11 and the list of supported devices will be displayed. This option
12 doesn't affect the kernel.
14 Please read the file <file:Documentation/input/joydev/joystick.rst> which
23 Say Y here if you have a joystick that connects to the PC
24 gameport. In addition to the usual PC analog joystick, this driver
30 Please read the file <file:Documentation/input/joydev/joystick.rst> which
33 To compile this driver as a module, choose M here: the
40 Say Y here if you have an FPGaming or MadCatz controller using the
41 A3D protocol over the PC gameport.
43 To compile this driver as a module, choose M here: the
48 depends on IIO
53 To compile this driver as a module, choose M here: the
54 module will be called adc-joystick.
59 depends on ADI!=m # avoid module name conflict
61 Say Y here if you have a Logitech controller using the ADI
62 protocol over the PC gameport.
64 To compile this driver as a module, choose M here: the
73 To compile this driver as a module, choose M here: the
83 To compile this driver as a module, choose M here: the
90 Say Y here if you have a Gravis controller using the GrIP protocol
91 over the PC gameport.
93 To compile this driver as a module, choose M here: the
100 Say Y here if you have the original Gravis GrIP MultiPort, a hub
101 that connects to the gameport and you connect gamepads to it.
103 To compile this driver as a module, choose M here: the
111 protocol over the PC gameport.
113 To compile this driver as a module, choose M here: the
121 communicating digitally over the gameport.
123 To compile this driver as a module, choose M here: the
130 Say Y here if you have a Microsoft controller using the Digital
133 To compile this driver as a module, choose M here: the
140 Say Y here if you have a ThrustMaster controller using the
141 DirectConnect (BSP) protocol over the PC gameport.
143 To compile this driver as a module, choose M here: the
155 To compile this driver as a module, choose M here: the
165 To compile this driver as a module, choose M here: the
175 To compile this driver as a module, choose M here: the
183 controller connected to your computer's serial port. For the
184 SpaceBall 4000 USB model, use the USB HID driver.
186 To compile this driver as a module, choose M here: the
196 To compile this driver as a module, choose M here: the
206 To compile this driver as a module, choose M here: the
210 tristate "5-byte Zhenhua RC transmitter"
214 Say Y here if you have a Zhen Hua PPM-4CH transmitter which is
215 supplied with a ready to fly micro electric indoor helicopters
219 To compile this driver as a module, choose M here: the
224 depends on PARPORT
227 gamepad, Sega Saturn gamepad, or a Multisystem -- Atari, Amiga,
229 For more information on how to use the driver please read
230 <file:Documentation/input/devices/joystick-parport.rst>.
232 To compile this driver as a module, choose M here: the
237 depends on PARPORT
242 Sony PlayStation gamepad or a Multisystem -- Atari, Amiga,
244 For more information on how to use the driver please read
245 <file:Documentation/input/devices/joystick-parport.rst>.
247 To compile this driver as a module, choose M here: the
252 depends on PARPORT
254 Say Y here if you have the TurboGraFX interface by Steffen Schwenke,
255 and want to use it with Multisystem -- Atari, Amiga, Commodore,
256 Amstrad CPC joystick. For more information on how to use the driver
257 please read <file:Documentation/input/devices/joystick-parport.rst>.
259 To compile this driver as a module, choose M here: the
264 depends on AMIGA
269 To compile this driver as a module, choose M here: the
274 depends on I2C
279 To compile this driver as a module, choose M here: the
286 Say Y here if you want to dump data from your joystick into the system
290 To compile this driver as a module, choose M here: the
294 tristate "X-Box gamepad support"
295 depends on USB_ARCH_HAS_HCD
298 Say Y here if you want to use the X-Box pad with your computer.
302 For information about how to connect the X-Box pad to USB, see
305 To compile this driver as a module, choose M here: the
309 bool "X-Box gamepad rumble support"
310 depends on JOYSTICK_XPAD && INPUT
317 depends on JOYSTICK_XPAD && (LEDS_CLASS=y || LEDS_CLASS=JOYSTICK_XPAD)
319 This option enables support for the LED which surrounds the Big X on
323 tristate "Walkera WK-0701 RC transmitter"
324 depends on HIGH_RES_TIMERS && PARPORT
326 Say Y or M here if you have a Walkera WK-0701 transmitter which is
327 supplied with a ready to fly Walkera helicopters such as HM36,
331 To compile this driver as a module, choose M here: the
336 depends on MAPLE
343 To compile this as a module choose M here: the module will be called
348 depends on SPI
353 To compile this driver as a module, choose M here: the
354 module will be called psxpad-spi.
358 depends on JOYSTICK_PSXPAD_SPI
368 depends on USB_ARCH_HAS_HCD
371 Say Y here if you want to use the PhoenixRC Flight Controller Adapter.
373 To compile this driver as a module, choose M here: the
378 depends on I2C
380 Say Y here if you want to use the SparkFun Qwiic Joystick.
382 To compile this driver as a module, choose M here: the
383 module will be called qwiic-joystick.
386 tristate "FlySky FS-iA6B RC Receiver"
389 Say Y here if you use a FlySky FS-i6 RC remote control along with the
390 FS-iA6B RC receiver as a joystick input device.
392 To compile this driver as a module, choose M here: the
397 depends on MACH_NINTENDO64
399 Say Y here if you want enable support for the four
400 built-in controller ports on the Nintendo 64 console.
404 depends on INPUT && I2C
405 depends on HAS_IOMEM
408 Say Y here if you want to enable the driver for the
409 the Raspberry Pi Sense HAT.
411 To compile this driver as a module, choose M here: the