1# 2# Gameport configuration 3# 4config GAMEPORT 5 tristate "Gameport support" 6 ---help--- 7 Gameport support is for the standard 15-pin PC gameport. If you 8 have a joystick, gamepad, gameport card, a soundcard with a gameport 9 or anything else that uses the gameport, say Y or M here and also to 10 at least one of the hardware specific drivers. 11 12 For Ensoniq AudioPCI (ES1370), AudioPCI 97 (ES1371), ESS Solo1, 13 S3 SonicVibes, Trident 4DWave, SiS7018, and ALi 5451 gameport 14 support is provided by the sound drivers, so you won't need any 15 from the below listed modules. You still need to say Y here. 16 17 If unsure, say Y. 18 19 To compile this driver as a module, choose M here: the 20 module will be called gameport. 21 22if GAMEPORT 23 24config GAMEPORT_NS558 25 tristate "Classic ISA and PnP gameport support" 26 help 27 Say Y here if you have an ISA or PnP gameport. 28 29 If unsure, say Y. 30 31 To compile this driver as a module, choose M here: the 32 module will be called ns558. 33 34config GAMEPORT_L4 35 tristate "PDPI Lightning 4 gamecard support" 36 help 37 Say Y here if you have a PDPI Lightning 4 gamecard. 38 39 To compile this driver as a module, choose M here: the 40 module will be called lightning. 41 42config GAMEPORT_EMU10K1 43 tristate "SB Live and Audigy gameport support" 44 depends on PCI 45 help 46 Say Y here if you have a SoundBlaster Live! or SoundBlaster 47 Audigy card and want to use its gameport. 48 49 To compile this driver as a module, choose M here: the 50 module will be called emu10k1-gp. 51 52config GAMEPORT_VORTEX 53 tristate "Aureal Vortex, Vortex 2 gameport support" 54 depends on PCI 55 help 56 Say Y here if you have an Aureal Vortex 1 or 2 card and want 57 to use its gameport. 58 59 To compile this driver as a module, choose M here: the 60 module will be called vortex. 61 62config GAMEPORT_FM801 63 tristate "ForteMedia FM801 gameport support" 64 depends on PCI 65 66config GAMEPORT_CS461X 67 tristate "Crystal SoundFusion gameport support" 68 depends on PCI 69 70endif 71 72# Yes, SOUND_GAMEPORT looks a bit odd. Yes, it ends up being turned on 73# in every .config. Please don't touch it. It is here to handle an 74# unusual dependency between GAMEPORT and sound drivers. 75# 76# Some sound drivers call gameport functions. If GAMEPORT is 77# not selected, empty stubs are provided for the functions and all is 78# well. 79# If GAMEPORT is built in, everything is fine. 80# If GAMEPORT is a module, however, it would need to be loaded for the 81# sound driver to be able to link properly. Therefore, the sound 82# driver must be a module as well in that case. Since there's no way 83# to express that directly in Kconfig, we use SOUND_GAMEPORT to 84# express it. SOUND_GAMEPORT boils down to "if GAMEPORT is 'm', 85# anything that depends on SOUND_GAMEPORT must be 'm' as well. if 86# GAMEPORT is 'y' or 'n', it can be anything". 87config SOUND_GAMEPORT 88 tristate 89 default m if GAMEPORT=m 90 default y 91