Lines Matching refs:the
9 under the terms of the GNU General Public License as published by the Free
10 Software Foundation; either version 2 of the License, or (at your option)
13 This program is distributed in the hope that it will be useful, but
14 WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY
15 or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for
18 You should have received a copy of the GNU General Public License along
19 with this program; if not, write to the Free Software Foundation, Inc., 59
22 Should you need to contact me, the author, you can do so either by e-mail
26 For your convenience, the GNU General Public License version 2 is included
27 in the package: See the file COPYING.
35 Should you encounter any problems while using the driver, or joysticks
43 There is also a mailing list for the driver at:
51 For basic usage you just choose the right options in kernel config and
57 utilities is available at the abovementioned website. I suggest you download
62 For applications to be able to use the joysticks,
86 For all joystick drivers to function, you'll need the userland interface
91 For gameport joysticks, you'll have to load the gameport driver as well;
95 And for serial port joysticks, you'll need the serial input line
96 discipline module loaded and the inputattach utility started:
101 In addition to that, you'll need the joystick driver module itself, most
116 For testing the joystick driver functionality, there is the jstest
117 program in the utilities package. You run it by typing:
121 And it should show a line with the joystick values, which update as you
122 move the stick, and press its buttons. The axes should all be zero when the
123 joystick is in the center position. They should not jitter by themselves to
125 the stick. They should have the full range from -32767 to 32767. If all this
126 is met, then it's all fine, and you can play the games. :)
128 If it's not, then there might be a problem. Try to calibrate the joystick,
129 and if it still doesn't work, read the drivers section of this file, the
130 troubleshooting section, and the FAQ.
134 For most joysticks you won't need any manual calibration, since the
135 joystick should be autocalibrated by the driver automagically. However, with
137 want better precision, you can use the jscal program
141 included in the joystick package to set better correction coefficients than
142 what the driver would choose itself.
144 After calibrating the joystick you can verify if you like the new
145 calibration using the jstest command, and if you do, you then can save the
154 This way, after the next reboot your joystick will remain calibrated. You
155 can also add the jscal -p line to your shutdown script.
160 In this section each of the separate hardware specific drivers is described.
164 The analog.c uses the standard analog inputs of the gameport, and thus
174 However the only types that can be autodetected are:
182 you'll need to specify the types either on the kernel command line or on the
183 module command line, when inserting analog into the kernel. The
188 'type' is type of the joystick from the table below, defining joysticks
189 present on gameports in the system, starting with gameport0, second 'type'
205 In case your joystick doesn't fit in any of the above categories, you can
206 specify the type as a number by combining the bits in the table below. This
243 Microsoft 'Digital Overdrive' protocol is supported by the sidewinder.c
256 There is one caveat with the 3D Pro. There are 9 buttons reported,
257 although the joystick has only 8. The 9th button is the mode switch on the
258 rear side of the joystick. However, moving it, you'll reset the joystick,
259 and make it unresponsive for about a one third of a second. Furthermore, the
260 joystick will also re-center itself, taking the position it was in during
264 by the analog driver described above.
268 Logitech ADI protocol is supported by the adi.c module. It should support
282 ADI devices are autodetected, and the driver supports up to two (any
288 handled by the analog driver described above. Logitech WingMan Warrior and
290 WingMan Force and Logitech WingMan Formula Force are supported by the
295 Gravis GrIP protocol is supported by the grip.c module. It currently
308 supported by the stinger driver. Other Gravis joysticks are supported by the
314 themselves and is licensed to MadCatz. A3D devices are supported by the
321 All these devices are autodetected. Because the Assassin 3D and the Panther
322 allow connecting analog joysticks to them, you'll need to load the analog
323 driver as well to handle the attached joysticks.
326 the USB documentation for how to setup an USB mouse.
330 The TM DirectConnect (BSP) protocol is supported by the tmdc.c
344 TMDC devices are autodetected, and thus no parameters to the module
350 The Blaster protocol is supported by the cobra.c module. It supports only
351 the:
359 The Genius digitally communicating joysticks are supported by the gf2k.c
371 The InterAct digitally communicating joysticks are supported by the
382 PDPI Lightning 4 gamecards are supported by the lightning.c module.
383 Once the module is loaded, the analog driver can be used to handle the
391 provide an "Enhanced Game Port" mode where the soundcard handles polling the
392 joystick. This mode is supported by the pcigame.c module. Once loaded the
393 analog driver can use the enhanced features of these gameports..
398 Port", much like the 4DWave or Vortex above. This, and also the normal mode
399 for the port of the SoundFusion is supported by the cs461x.c module.
405 its ISA counterparts. It also requires special support, hence the
406 emu10k1-gp.c module for it instead of the normal ns558.c one.
410 These PCI soundcards have specific gameports. They are handled by the
411 sound drivers themselves. Make sure you select gameport support in the
412 joystick menu and sound card support in the sound menu for your appropriate
417 Amiga joysticks, connected to an Amiga, are supported by the amijoy.c
418 driver. Since they can't be autodetected, the driver has a command line.
422 a and b define the joysticks connected to the JOY0DAT and JOY1DAT ports of
423 the Amiga.
430 No more joystick types are supported now, but that should change in the
431 future if I get an Amiga in the reach of my fingers.
439 SpaceTec serial devices communicate using the SpaceWare protocol. It is
440 supported by the spaceorb.c and spaceball.c drivers. The devices currently
450 In addition to having the spaceorb/spaceball and serport modules in the
451 kernel, you also need to attach a serial port to it. to do that, run the
458 where /dev/tts/x is the serial port which the device is connected to. After
459 doing this, the device will be reported and will start working.
461 There is one caveat with the SpaceOrb. The button #6, the on the bottom
462 side of the orb, although reported as an ordinary button, causes internal
463 recentering of the spaceorb, moving the zero point to the position in which
464 the ball is at the moment of pressing the button. So, think first before
471 The SWIFT serial protocol is supported by the warrior.c module. It
472 currently supports only the:
476 but in the future, Logitech CyberMan (the original one, not CM2) could be
477 supported as well. To use the module, you need to run inputattach after you
478 insert/compile the module into your kernel:
482 /dev/tts/x is the serial port your Warrior is attached to.
487 Systems), for many other companies (Logitech, HP, ...) is supported by the
488 joy-magellan module. It currently supports only the:
493 models, the additional buttons on the 'Plus' versions are not supported yet.
495 To use it, you need to attach the serial port to the driver using the
499 command. After that the Magellan will be detected, initialized, will beep,
500 and the /dev/input/jsX device should become usable.
504 All I-Force devices are supported by the iforce module. This includes:
515 To use it, you need to attach the serial port to the driver using the
519 command. After that the I-Force device will be detected, and the
522 In case you're using the device via the USB port, the inputattach command
525 The I-Force driver now supports force feedback via the event interface.
534 computers, is supported by the stinger.c module. To use it, attach the
535 serial port to the driver using:
539 where x is the number of the serial port.
544 testing whether the driver works, if in doubt, use the jstest utility in
545 some of its modes. The most useful modes are "normal" - for the 1.x
546 interface, and "old" for the "0.x" interface. You run it by typing:
551 Additionally you can do a test with the evtest utility:
555 Oh, and read the FAQ! :)
559 Q: Running 'jstest /dev/input/js0' results in "File not found" error. What's the
564 or pad that uses a 9-pin D-type cannon connector to the serial port of my
566 A: Yes, it is possible, but it'll burn your serial port or the pad. It
569 Q: My joystick doesn't work with Quake / Quake 2. What's the cause?
575 The 1.0 driver uses a new, event based approach to the joystick driver.
576 Instead of the user program polling for the joystick values, the joystick
578 joystick.h and jstest.c included in the joystick package for more
582 For backward compatibility the old (v0.x) interface is still included.
583 Any call to the joystick driver using the old interface will return values
584 that are compatible to the old interface. This interface is still limited
586 the driver provides up to 32.