Linux Joystick Support

Joystick 지원, 기본 사용과 calibration

Linux joystick driver는 다양한 joystick과 유사 장치를 지원하며 Linux의 모든 input device를 지원하려는 더 큰 input subsystem project의 일부입니다. 문서에 적힌 project mailing list는 `linux-input@vger.kernel.org`입니다.

기본 사용은 kernel configuration에서 알맞은 option을 선택하는 것으로 시작합니다. 시험과 serial 장치 연결에는 보통 `joystick`, `input-utils`, `evtest` package에 포함된 `jstest`, `jscal`, `evtest`가 필요하고 serial port joystick에는 `inputattach`가 필수입니다.

Application이 joystick을 사용하려면 `/dev/input/jsN` node가 있어야 합니다. 보통 system이 자동 생성하지만 수동으로는 major 13, minor 0~3으로 `js0`~`js3`를 만들고 필요하면 `/dev/jsN` symbolic link를 둡니다. Input utility 시험용 `event0`~`event3`은 major 13, minor 64~67입니다.

모든 joystick driver에는 사용자 공간 interface인 `joydev`가 필요합니다. Gameport joystick은 `ns558`, serial joystick은 `serport`와 `inputattach`, 일반 analog joystick은 `analog` module도 필요합니다.

자동 module load 예는 `tty-ldisc-2`를 `serport`, character major 13을 `input`에 연결하고 input 위에 `joydev ns558 analog`를 load하며 `analog map=gamepad,none,2btn` option을 설정합니다. 실제 system에 맞게 조정해야 합니다.

`jstest /dev/input/js0`은 stick 이동과 button press에 따라 갱신되는 값을 보여야 합니다. 중앙에서 모든 axis는 0이고 스스로 가까운 값 사이를 흔들리지 않아야 하며 다른 위치에서도 안정적이어야 합니다. 전체 범위는 -32767부터 32767입니다.

이 조건을 만족하지 않으면 먼저 calibration하고 계속 실패하면 driver 절, troubleshooting, FAQ를 확인합니다. 대부분은 driver가 자동 보정하지만 비선형 resistor analog joystick이나 더 높은 정밀도가 필요하면 `jscal -c /dev/input/js0`로 correction coefficient를 조정합니다.

새 보정은 `jstest`로 확인하고 만족하면 `jscal -p /dev/input/js0 > /etc/joystick.cal`로 저장합니다. Boot rc script에서 `source /etc/joystick.cal`을 실행하면 reboot 뒤에도 유지되며, shutdown script에 `jscal -p` 저장 명령을 넣을 수도 있습니다.

.. include:: <isonum.txt>

.. _joystick-doc:

Introduction
============

The joystick driver for Linux provides support for a variety of joysticks
and similar devices. It is based on a larger project aiming to support all
input devices in Linux.

The mailing list for the project is:

        linux-input@vger.kernel.org

send "subscribe linux-input" to majordomo@vger.kernel.org to subscribe to it.

Usage
=====

For basic usage you just choose the right options in kernel config and
you should be set.

Utilities
---------

For testing and other purposes (for example serial devices), there is a set
of utilities, such as ``jstest``, ``jscal``, and ``evtest``,
usually packaged as ``joystick``, ``input-utils``, ``evtest``, and so on.

``inputattach`` utility is required if your joystick is connected to a
serial port.

Device nodes
------------

For applications to be able to use the joysticks, device nodes should be
created in /dev. Normally it is done automatically by the system, but
it can also be done by hand::

    cd /dev
    rm js*
    mkdir input
    mknod input/js0 c 13 0
    mknod input/js1 c 13 1
    mknod input/js2 c 13 2
    mknod input/js3 c 13 3
    ln -s input/js0 js0
    ln -s input/js1 js1
    ln -s input/js2 js2
    ln -s input/js3 js3

For testing with inpututils it's also convenient to create these::

    mknod input/event0 c 13 64
    mknod input/event1 c 13 65
    mknod input/event2 c 13 66
    mknod input/event3 c 13 67

Modules needed
--------------

For all joystick drivers to function, you'll need the userland interface
module in kernel, either loaded or compiled in::

        modprobe joydev

For gameport joysticks, you'll have to load the gameport driver as well::

        modprobe ns558

And for serial port joysticks, you'll need the serial input line
discipline module loaded and the inputattach utility started::

        modprobe serport
        inputattach -xxx /dev/tts/X &

In addition to that, you'll need the joystick driver module itself, most
usually you'll have an analog joystick::

        modprobe analog

For automatic module loading, something like this might work - tailor to
your needs::

        alias tty-ldisc-2 serport
        alias char-major-13 input
        above input joydev ns558 analog
        options analog map=gamepad,none,2btn

Verifying that it works
-----------------------

For testing the joystick driver functionality, there is the jstest
program in the utilities package. You run it by typing::

        jstest /dev/input/js0

And it should show a line with the joystick values, which update as you
move the stick, and press its buttons. The axes should all be zero when the
joystick is in the center position. They should not jitter by themselves to
other close values, and they also should be steady in any other position of
the stick. They should have the full range from -32767 to 32767. If all this
is met, then it's all fine, and you can play the games. :)

If it's not, then there might be a problem. Try to calibrate the joystick,
and if it still doesn't work, read the drivers section of this file, the
troubleshooting section, and the FAQ.

Calibration
-----------

For most joysticks you won't need any manual calibration, since the
joystick should be autocalibrated by the driver automagically. However, with
some analog joysticks, that either do not use linear resistors, or if you
want better precision, you can use the jscal program::

        jscal -c /dev/input/js0

included in the joystick package to set better correction coefficients than
what the driver would choose itself.

After calibrating the joystick you can verify if you like the new
calibration using the jstest command, and if you do, you then can save the
correction coefficients into a file::

        jscal -p /dev/input/js0 > /etc/joystick.cal

And add a line to your rc script executing that file::

        source /etc/joystick.cal

This way, after the next reboot your joystick will remain calibrated. You
can also add the ``jscal -p`` line to your shutdown script.

Analog joystick driver와 `analog.map`

`analog.c` driver는 표준 gameport analog input을 사용해 모든 표준 joystick과 gamepad를 지원합니다. 높은 data precision을 제공하며 CH Flightstick Pro, ThrustMaster FCS 호환 추가 hat·button, 6·8 button gamepad, 확장된 CHF 계열인 Saitek Cyborg digital joystick도 처리합니다.

자동 탐지 가능한 것은 2-axis 4-button, 3-axis 4-button, 4-axis 4-button joystick과 Saitek Cyborg digital joystick입니다. Axis·hat·button 수가 다른 장치는 kernel command line 또는 `analog` module load 때 `analog.map=<type1>,<type2>,...`로 지정합니다.

각 `type`은 system의 gameport 순서에 대응합니다. 첫 entry는 gameport0, 두 번째는 gameport1의 joystick type입니다.

사전 정의 type에 맞지 않으면 아래 bit를 조합한 숫자로 type을 만들 수 있지만 구조를 정확히 알 때만 권장됩니다. 위험하지는 않지만 단순하지 않습니다.

Hardware-specific driver information
====================================

In this section each of the separate hardware specific drivers is described.

Analog joysticks
----------------

The analog.c driver uses the standard analog inputs of the gameport, and thus
supports all standard joysticks and gamepads. It uses a very advanced
routine for this, allowing for data precision that can't be found on any
other system.

It also supports extensions like additional hats and buttons compatible
with CH Flightstick Pro, ThrustMaster FCS or 6 and 8 button gamepads. Saitek
Cyborg 'digital' joysticks are also supported by this driver, because
they're basically souped up CHF sticks.

However the only types that can be autodetected are:

* 2-axis, 4-button joystick
* 3-axis, 4-button joystick
* 4-axis, 4-button joystick
* Saitek Cyborg 'digital' joysticks

For other joystick types (more/less axes, hats, and buttons) support
you'll need to specify the types either on the kernel command line or on the
module command line, when inserting analog into the kernel. The
parameters are::

        analog.map=<type1>,<type2>,<type3>,....

'type' is type of the joystick from the table below, defining joysticks
present on gameports in the system, starting with gameport0, second 'type'
entry defining joystick on gameport1 and so on.

        ========= =====================================================
        Type      Meaning
        ========= =====================================================
        none      No analog joystick on that port
        auto      Autodetect joystick
        2btn      2-button n-axis joystick
        y-joy     Two 2-button 2-axis joysticks on an Y-cable
        y-pad     Two 2-button 2-axis gamepads on an Y-cable
        fcs       Thrustmaster FCS compatible joystick
        chf       Joystick with a CH Flightstick compatible hat
        fullchf   CH Flightstick compatible with two hats and 6 buttons
        gamepad   4/6-button n-axis gamepad
        gamepad8  8-button 2-axis gamepad
        ========= =====================================================

In case your joystick doesn't fit in any of the above categories, you can
specify the type as a number by combining the bits in the table below. This
is not recommended unless you really know what are you doing. It's not
dangerous, but not simple either.

        ==== =========================
        Bit  Meaning
        ==== =========================
         0   Axis X1
         1   Axis Y1
         2   Axis X2
         3   Axis Y2
         4   Button A
         5   Button B
         6   Button C
         7   Button D
         8   CHF Buttons X and Y
         9   CHF Hat 1
        10   CHF Hat 2
        11   FCS Hat
        12   Pad Button X
        13   Pad Button Y
        14   Pad Button U
        15   Pad Button V
        16   Saitek F1-F4 Buttons
        17   Saitek Digital Mode
        19   GamePad
        20   Joy2 Axis X1
        21   Joy2 Axis Y1
        22   Joy2 Axis X2
        23   Joy2 Axis Y2
        24   Joy2 Button A
        25   Joy2 Button B
        26   Joy2 Button C
        27   Joy2 Button D
        31   Joy2 GamePad
        ==== =========================

Gameport digital protocol 장치

Microsoft Digital Overdrive protocol은 `sidewinder.c`가 지원하며 SideWinder 3D Pro, Force Feedback Pro, Force Feedback Wheel, FreeStyle Pro, 최대 네 개를 chain할 수 있는 GamePad, Precision Pro, Precision Pro USB를 자동 탐지합니다. Module parameter는 필요 없습니다.

SideWinder 3D Pro는 물리 button이 8개지만 mode switch를 아홉 번째 button으로 보고합니다. Switch를 움직이면 joystick이 reset되어 약 1/3초 응답하지 않고 그 순간 위치를 새 center로 삼으므로 다른 기능에 연결하기 전에 주의해야 합니다. SideWinder Standard는 digital이 아니어서 `analog` driver가 처리합니다.

Logitech ADI protocol은 `adi.c`가 지원하며 한 gameport에 Y-cable 또는 chain으로 임의 조합 두 장치까지 자동 탐지합니다.

WingMan Joystick, Attack, Extreme, ThunderPad는 digital이 아니어서 `analog`가 처리합니다. WingMan Warrior와 Magellan은 뒤에서 설명하는 serial driver, WingMan Force와 Formula Force는 I-Force driver가 처리합니다. 원본 CyberMan은 아직 지원하지 않습니다.

Gravis GrIP protocol은 `grip.c`가 GamePad Pro, BlackHawk Digital, Xterminator, Xterminator DualControl을 자동 탐지하며 한 gameport에 chain 또는 Y-cable로 임의 조합 두 개까지 지원합니다. GrIP MultiPort는 미지원, Stinger는 serial `stinger`, 그 밖의 Gravis joystick은 `analog`가 처리합니다.

FPGaming의 Assassin 3D protocol은 MadCatz에도 license되었으며 `a3d.c`가 FPGaming Assassin 3D, MadCatz Panther, Panther XL을 자동 탐지합니다. Assassin 3D와 Panther에 연결한 analog joystick을 처리하려면 `analog` driver도 load해야 합니다. Trackball은 USB `mousedev`에서 일반 mouse로 동작해야 합니다.

Microsoft SideWinder joysticks
------------------------------

Microsoft 'Digital Overdrive' protocol is supported by the sidewinder.c
module. All currently supported joysticks:

* Microsoft SideWinder 3D Pro
* Microsoft SideWinder Force Feedback Pro
* Microsoft SideWinder Force Feedback Wheel
* Microsoft SideWinder FreeStyle Pro
* Microsoft SideWinder GamePad (up to four, chained)
* Microsoft SideWinder Precision Pro
* Microsoft SideWinder Precision Pro USB

are autodetected, and thus no module parameters are needed.

There is one caveat with the 3D Pro. There are 9 buttons reported,
although the joystick has only 8. The 9th button is the mode switch on the
rear side of the joystick. However, moving it, you'll reset the joystick,
and make it unresponsive for about a one third of a second. Furthermore, the
joystick will also re-center itself, taking the position it was in during
this time as a new center position. Use it if you want, but think first.

The SideWinder Standard is not a digital joystick, and thus is supported
by the analog driver described above.

Logitech ADI devices
--------------------

Logitech ADI protocol is supported by the adi.c module. It should support
any Logitech device using this protocol. This includes, but is not limited
to:

* Logitech CyberMan 2
* Logitech ThunderPad Digital
* Logitech WingMan Extreme Digital
* Logitech WingMan Formula
* Logitech WingMan Interceptor
* Logitech WingMan GamePad
* Logitech WingMan GamePad USB
* Logitech WingMan GamePad Extreme
* Logitech WingMan Extreme Digital 3D

ADI devices are autodetected, and the driver supports up to two (any
combination of) devices on a single gameport, using a Y-cable or chained
together.

Logitech WingMan Joystick, Logitech WingMan Attack, Logitech WingMan
Extreme and Logitech WingMan ThunderPad are not digital joysticks and are
handled by the analog driver described above. Logitech WingMan Warrior and
Logitech Magellan are supported by serial drivers described below.  Logitech
WingMan Force and Logitech WingMan Formula Force are supported by the
I-Force driver described below. Logitech CyberMan is not supported yet.

Gravis GrIP
-----------

Gravis GrIP protocol is supported by the grip.c module. It currently
supports:

* Gravis GamePad Pro
* Gravis BlackHawk Digital
* Gravis Xterminator
* Gravis Xterminator DualControl

All these devices are autodetected, and you can even use any combination
of up to two of these pads either chained together or using a Y-cable on a
single gameport.

GrIP MultiPort isn't supported yet. Gravis Stinger is a serial device and is
supported by the stinger driver. Other Gravis joysticks are supported by the
analog driver.

FPGaming A3D and MadCatz A3D
----------------------------

The Assassin 3D protocol created by FPGaming, is used both by FPGaming
themselves and is licensed to MadCatz. A3D devices are supported by the
a3d.c module. It currently supports:

* FPGaming Assassin 3D
* MadCatz Panther
* MadCatz Panther XL

All these devices are autodetected. Because the Assassin 3D and the Panther
allow connecting analog joysticks to them, you'll need to load the analog
driver as well to handle the attached joysticks.

The trackball should work with USB mousedev module as a normal mouse. See
the USB documentation for how to setup a USB mouse.

기타 gameport, soundcard와 platform 장치

ThrustMaster DirectConnect(BSP) protocol은 `tmdc.c`가 Millennium 3D Interceptor, 3D Rage Pad, Fusion Digital Game Pad를 지원합니다. FragMaster와 Attack Throttle은 직접 지원 대상으로 명시되지는 않았지만 동작할 가능성이 있어 사용자는 maintainer에게 결과를 알려야 합니다. 장치는 자동 탐지되고 Y-cable로 한 gameport에 두 개까지 연결합니다.

Creative Blaster protocol은 `cobra.c`가 Creative Blaster GamePad Cobra만 지원하며 Y-cable로 한 gameport에 두 개까지 사용할 수 있습니다. Genius digital joystick은 `gf2k.c`가 Flight2000 F-23, F-31, G-09D를 지원합니다. 다른 Genius digital 장치는 아직 미지원이지만 지원 추가는 비교적 쉽습니다.

InterAct digital joystick은 `interact.c`가 HammerHead/FX와 ProPad8 gamepad를 지원하며 다른 장치는 아직 미지원입니다.

PDPI Lightning 4 card는 `lightning.c`를 load한 뒤 `analog` driver로 joystick을 처리합니다. Digital joystick은 port 0에서만 동작합니다. Y-cable을 쓰면 L4 card 한 장에 analog joystick 8개, 두 장이면 16개까지 연결할 수 있습니다.

Trident 4DWave DX/NX와 Aureal Vortex/Vortex2 soundcard의 Enhanced Game Port는 card가 joystick polling을 수행하며 `pcigame.c`가 지원합니다. Load 후 `analog` driver가 향상된 기능을 사용합니다. Crystal SoundFusion의 Enhanced와 normal mode gameport는 `cs461x.c`가 처리합니다.

SoundBlaster Live!의 PCI gameport는 enhanced 기능은 없지만 ISA보다 빠르고 특별 지원이 필요해 `ns558.c` 대신 `emu10k1-gp.c`를 사용합니다. SoundBlaster 64·128의 ES1370·ES1371, ESS Solo1, S3 SonicVibes PCI soundcard gameport는 sound driver 자체가 처리하므로 joystick menu의 gameport 지원과 해당 sound card 지원을 함께 선택합니다.

Amiga joystick은 `amijoy.c`가 지원하지만 자동 탐지할 수 없어 `amijoy.map=<a>,<b>`를 사용합니다. a와 b는 `JOY0DAT`, `JOY1DAT` port에 연결된 장치를 나타내며 0은 없음, 1은 1-button digital joystick입니다.

Game console과 8-bit pad·joystick은 PC용이 아니어서 parallel port용 특수 connector가 보통 필요합니다. 자세한 내용은 `joystick-parport` 문서를 참고합니다.

ThrustMaster DirectConnect (BSP)
--------------------------------

The TM DirectConnect (BSP) protocol is supported by the tmdc.c
module. This includes, but is not limited to:

* ThrustMaster Millennium 3D Interceptor
* ThrustMaster 3D Rage Pad
* ThrustMaster Fusion Digital Game Pad

Devices not directly supported, but hopefully working are:

* ThrustMaster FragMaster
* ThrustMaster Attack Throttle

If you have one of these, contact me.

TMDC devices are autodetected, and thus no parameters to the module
are needed. Up to two TMDC devices can be connected to one gameport, using
a Y-cable.

Creative Labs Blaster
---------------------

The Blaster protocol is supported by the cobra.c module. It supports only
the:

* Creative Blaster GamePad Cobra

Up to two of these can be used on a single gameport, using a Y-cable.

Genius Digital joysticks
------------------------

The Genius digitally communicating joysticks are supported by the gf2k.c
module. This includes:

* Genius Flight2000 F-23 joystick
* Genius Flight2000 F-31 joystick
* Genius G-09D gamepad

Other Genius digital joysticks are not supported yet, but support can be
added fairly easily.

InterAct Digital joysticks
--------------------------

The InterAct digitally communicating joysticks are supported by the
interact.c module. This includes:

* InterAct HammerHead/FX gamepad
* InterAct ProPad8 gamepad

Other InterAct digital joysticks are not supported yet, but support can be
added fairly easily.

PDPI Lightning 4 gamecards
--------------------------

PDPI Lightning 4 gamecards are supported by the lightning.c module.
Once the module is loaded, the analog driver can be used to handle the
joysticks. Digitally communicating joystick will work only on port 0, while
using Y-cables, you can connect up to 8 analog joysticks to a single L4
card, 16 in case you have two in your system.

Trident 4DWave / Aureal Vortex
------------------------------

Soundcards with a Trident 4DWave DX/NX or Aureal Vortex/Vortex2 chipset
provide an "Enhanced Game Port" mode where the soundcard handles polling the
joystick.  This mode is supported by the pcigame.c module. Once loaded the
analog driver can use the enhanced features of these gameports..

Crystal SoundFusion
-------------------

Soundcards with Crystal SoundFusion chipsets provide an "Enhanced Game
Port", much like the 4DWave or Vortex above. This, and also the normal mode
for the port of the SoundFusion is supported by the cs461x.c module.

SoundBlaster Live!
------------------

The Live! has a special PCI gameport, which, although it doesn't provide
any "Enhanced" stuff like 4DWave and friends, is quite a bit faster than
its ISA counterparts. It also requires special support, hence the
emu10k1-gp.c module for it instead of the normal ns558.c one.

SoundBlaster 64 and 128 - ES1370 and ES1371, ESS Solo1 and S3 SonicVibes
------------------------------------------------------------------------

These PCI soundcards have specific gameports. They are handled by the
sound drivers themselves. Make sure you select gameport support in the
joystick menu and sound card support in the sound menu for your appropriate
card.

Amiga
-----

Amiga joysticks, connected to an Amiga, are supported by the amijoy.c
driver. Since they can't be autodetected, the driver has a command line:

        amijoy.map=<a>,<b>

a and b define the joysticks connected to the JOY0DAT and JOY1DAT ports of
the Amiga.

        ====== ===========================
        Value  Joystick type
        ====== ===========================
          0    None
          1    1-button digital joystick
        ====== ===========================

No more joystick types are supported now, but that should change in the
future if I get an Amiga in the reach of my fingers.

Game console and 8-bit pads and joysticks
-----------------------------------------

These pads and joysticks are not designed for PCs and other computers
Linux runs on, and usually require a special connector for attaching
them through a parallel port.

See :ref:`joystick-parport` for more info.

Serial, SpaceTec, SWIFT, Magellan과 I-Force

SpaceTec serial 장치는 SpaceWare protocol을 사용합니다. `spaceorb.c`는 SpaceBall Avenger와 SpaceOrb 360, `spaceball.c`는 SpaceBall 4000 FLX를 지원합니다. Kernel에 해당 module과 `serport`를 넣고 `inputattach --spaceorb /dev/tts/x` 또는 `--spaceball`을 실행하면 장치를 탐지해 동작시킵니다.

SpaceOrb 아래쪽 button #6은 일반 button으로 보고되지만 눌렀을 때 내부 recentering을 수행해 그 순간 ball 위치를 새 zero point로 삼습니다. 다른 기능에 bind할 때 주의해야 합니다. SpaceBall 2003 FLX와 3003 FLX는 아직 지원하지 않습니다.

Logitech SWIFT serial protocol은 `warrior.c`가 WingMan Warrior만 지원합니다. Module을 넣은 뒤 `inputattach --warrior /dev/tts/x`를 실행합니다. 향후 원본 Logitech CyberMan도 지원될 수 있습니다.

LogiCad3d가 여러 회사에 공급한 Magellan 또는 Space Mouse는 `joy-magellan` module이 Magellan 3D와 Space Mouse를 지원하지만 Plus version의 추가 button은 아직 지원하지 않습니다. `inputattach --magellan /dev/tts/x` 뒤 장치가 탐지·초기화되고 beep하며 `/dev/input/jsX`가 사용 가능해집니다.

모든 I-Force 장치는 `iforce` module이 지원합니다.

Serial I-Force는 `inputattach --iforce /dev/tts/x`를 실행하면 탐지되고 `/dev/input/jsX`가 사용 가능해집니다. USB 연결이면 `inputattach`가 필요 없습니다. I-Force driver는 event interface를 통한 force feedback을 지원합니다.

Logitech WingMan 3D는 I-Force가 아니라 HID가 지원하며 force feedback은 지원하지 않습니다. Logitech gamepad도 HID 장치입니다.

Laptop용 Gravis Stinger serial gamepad는 `stinger.c`가 지원합니다. `inputattach --stinger /dev/tty/x`를 사용하며 x는 serial port 번호입니다.

SpaceTec/LabTec devices
-----------------------

SpaceTec serial devices communicate using the SpaceWare protocol. It is
supported by the spaceorb.c and spaceball.c drivers. The devices currently
supported by spaceorb.c are:

* SpaceTec SpaceBall Avenger
* SpaceTec SpaceOrb 360

Devices currently supported by spaceball.c are:

* SpaceTec SpaceBall 4000 FLX

In addition to having the spaceorb/spaceball and serport modules in the
kernel, you also need to attach a serial port to it. To do that, run the
inputattach program::

        inputattach --spaceorb /dev/tts/x &

or::

        inputattach --spaceball /dev/tts/x &

where /dev/tts/x is the serial port which the device is connected to. After
doing this, the device will be reported and will start working.

There is one caveat with the SpaceOrb. The button #6, the one on the bottom
side of the orb, although reported as an ordinary button, causes internal
recentering of the spaceorb, moving the zero point to the position in which
the ball is at the moment of pressing the button. So, think first before
you bind it to some other function.

SpaceTec SpaceBall 2003 FLX and 3003 FLX are not supported yet.

Logitech SWIFT devices
----------------------

The SWIFT serial protocol is supported by the warrior.c module. It
currently supports only the:

* Logitech WingMan Warrior

but in the future, Logitech CyberMan (the original one, not CM2) could be
supported as well. To use the module, you need to run inputattach after you
insert/compile the module into your kernel::

        inputattach --warrior /dev/tts/x &

/dev/tts/x is the serial port your Warrior is attached to.

Magellan / Space Mouse
----------------------

The Magellan (or Space Mouse), manufactured by LogiCad3d (formerly Space
Systems), for many other companies (Logitech, HP, ...) is supported by the
joy-magellan module. It currently supports only the:

* Magellan 3D
* Space Mouse

models; the additional buttons on the 'Plus' versions are not supported yet.

To use it, you need to attach the serial port to the driver using the::

        inputattach --magellan /dev/tts/x &

command. After that the Magellan will be detected, initialized, will beep,
and the /dev/input/jsX device should become usable.

I-Force devices
---------------

All I-Force devices are supported by the iforce module. This includes:

* AVB Mag Turbo Force
* AVB Top Shot Pegasus
* AVB Top Shot Force Feedback Racing Wheel
* Boeder Force Feedback Wheel
* Logitech WingMan Force
* Logitech WingMan Force Wheel
* Guillemot Race Leader Force Feedback
* Guillemot Force Feedback Racing Wheel
* Thrustmaster Motor Sport GT

To use it, you need to attach the serial port to the driver using the::

        inputattach --iforce /dev/tts/x &

command. After that the I-Force device will be detected, and the
/dev/input/jsX device should become usable.

In case you're using the device via the USB port, the inputattach command
isn't needed.

The I-Force driver now supports force feedback via the event interface.

Please note that Logitech WingMan 3D devices are _not_ supported by this
module, rather by hid. Force feedback is not supported for those devices.
Logitech gamepads are also hid devices.

Gravis Stinger gamepad
----------------------

The Gravis Stinger serial port gamepad, designed for use with laptop
computers, is supported by the stinger.c module. To use it, attach the
serial port to the driver using::

        inputattach --stinger /dev/tty/x &

where x is the number of the serial port.

문제 해결과 FAQ

문제가 의심되면 `jstest`의 `--normal` mode로 1.x interface, `--old` mode로 0.x interface를 시험합니다. Generic event는 `evtest /dev/input/event0`으로 확인하고 FAQ도 읽어야 합니다.

`jstest /dev/input/js0`이 `File not found`를 반환하면 device file이 없는 것이므로 앞의 device node 절에 따라 생성해야 합니다.

Atari·Commodore·Amiga·console의 9-pin D-type Cannon connector joystick을 PC serial port에 직접 연결해서는 안 됩니다. 동작하지 않을 뿐 아니라 serial port 또는 pad를 손상시킵니다.

Quake와 Quake 2는 joystick을 지원하지 않습니다. `joy2key`로 joystick 입력을 keypress로 변환해야 합니다.

Troubleshooting
===============

There is quite a high probability that you run into some problems. For
testing whether the driver works, if in doubt, use the jstest utility in
some of its modes. The most useful modes are "normal" - for the 1.x
interface, and "old" for the "0.x" interface. You run it by typing::

        jstest --normal /dev/input/js0
        jstest --old    /dev/input/js0

Additionally you can do a test with the evtest utility::

        evtest /dev/input/event0

Oh, and read the FAQ! :)

FAQ
===

:Q: Running 'jstest /dev/input/js0' results in "File not found" error. What's the
    cause?
:A: The device files don't exist. Create them (see section 2.2).

:Q: Is it possible to connect my old Atari/Commodore/Amiga/console joystick
    or pad that uses a 9-pin D-type Cannon connector to the serial port of my
    PC?
:A: Yes, it is possible, but it'll burn your serial port or the pad. It
    won't work, of course.

:Q: My joystick doesn't work with Quake / Quake 2. What's the cause?
:A: Quake / Quake 2 don't support joystick. Use joy2key to simulate keypresses
    for them.