linux-kernel - Proper support for Saitek X36F joystick

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 27 Oct 2020 13:42:35 +0100
From:   Pavel Machek <pavel@....cz>
To:     jkosina@...e.cz, dmitry.torokhov@...il.com, vojtech@...e.cz,
        linux-input@...r.kernel.org,
        kernel list <linux-kernel@...r.kernel.org>
Subject: Proper support for Saitek X36F joystick

Hi!

This is from 4.19, but I doubt this changed recently.

Saitek X36F+X35T combination is detected like this... in short one
hat, no switches, and lot of buttons.

In reality, combination has 4 four-way switches (hats?), 2 slider
switches (three positions) and lot less buttons. Sliders and 3 of 4
hats are detected as groups of buttons. Last hat is strange, I can't
see anything that corresponds to it on evtest, and as long as it is
pushed in any direction, all the other events stop. (It is also one
I'd like to use).

What needs to be done to get more useful mapping for userspace?

Is there any easy way to debug the hat that breaks everything?

Best regards,
								Pavel

$ evtest /dev/input/by-id/usb-Saitek_Saitek_X36_00103464-event-joystick
Input driver version is 1.0.1
Input device ID: bus 0x3 vendor 0x6a3 product 0x53f version 0x100
Input device name: "Saitek Saitek X36"
Supported events:
  Event type 0 (EV_SYN)
  Event type 1 (EV_KEY)
    Event code 288 (BTN_TRIGGER)
    Event code 289 (BTN_THUMB)
    Event code 290 (BTN_THUMB2)
    Event code 291 (BTN_TOP)
    Event code 292 (BTN_TOP2)
    Event code 293 (BTN_PINKIE)
    Event code 294 (BTN_BASE)
    Event code 295 (BTN_BASE2)
    Event code 296 (BTN_BASE3)
    Event code 297 (BTN_BASE4)
    Event code 298 (BTN_BASE5)
    Event code 299 (BTN_BASE6)
    Event code 300 (?)
    Event code 301 (?)
    Event code 302 (?)
    Event code 303 (BTN_DEAD)
    Event code 704 (BTN_TRIGGER_HAPPY1)
    Event code 705 (BTN_TRIGGER_HAPPY2)
    Event code 706 (BTN_TRIGGER_HAPPY3)
    Event code 707 (BTN_TRIGGER_HAPPY4)
    Event code 708 (BTN_TRIGGER_HAPPY5)
    Event code 709 (BTN_TRIGGER_HAPPY6)
    Event code 710 (BTN_TRIGGER_HAPPY7)
    Event code 711 (BTN_TRIGGER_HAPPY8)
    Event code 712 (BTN_TRIGGER_HAPPY9)
    Event code 713 (BTN_TRIGGER_HAPPY10)
  Event type 3 (EV_ABS)
    Event code 0 (ABS_X)
      Value    211
      Min       76
      Max      364
      Flat      18
    Event code 1 (ABS_Y)
      Value    219
      Min       76
      Max      404
      Flat      20
    Event code 3 (ABS_RX)
      Value    225
      Min        1
      Max      225
      Flat      14
    Event code 5 (ABS_RZ)
      Value    156
      Min       21
      Max      241
      Flat      13
    Event code 6 (ABS_THROTTLE)
      Value    235
      Min       21
      Max      235
      Flat      13
    Event code 7 (ABS_RUDDER)
      Value      1
      Min        1
      Max      209
      Flat      13
    Event code 16 (ABS_HAT0X)
      Value      0
      Min       -1
      Max        1
    Event code 17 (ABS_HAT0Y)
      Value      0
      Min       -1
      Max        1
  Event type 4 (EV_MSC)
    Event code 4 (MSC_SCAN)
Properties:
Testing ... (interrupt to exit)

-- 
http://www.livejournal.com/~pavelmachek

Download attachment "signature.asc" of type "application/pgp-signature" (196 bytes)