evemu-describe data for Microsoft X-Box One Elite 2 pad bcdVersion 4.07

[iacore]

@smcv here's the data

# EVEMU 1.3
# Kernel: 6.3.6-zen1-1-zen
# DMI: :)
# Input device name: "Microsoft X-Box One Elite 2 pad"
# Input device ID: bus 0x03 vendor 0x45e product 0xb00 version 0x407
# Supported events:
#   Event type 0 (EV_SYN)
#     Event code 0 (SYN_REPORT)
#     Event code 1 (SYN_CONFIG)
#     Event code 2 (SYN_MT_REPORT)
#     Event code 3 (SYN_DROPPED)
#     Event code 4 ((null))
#     Event code 5 ((null))
#     Event code 6 ((null))
#     Event code 7 ((null))
#     Event code 8 ((null))
#     Event code 9 ((null))
#     Event code 10 ((null))
#     Event code 11 ((null))
#     Event code 12 ((null))
#     Event code 13 ((null))
#     Event code 14 ((null))
#     Event code 15 (SYN_MAX)
#   Event type 1 (EV_KEY)
#     Event code 304 (BTN_SOUTH)
#     Event code 305 (BTN_EAST)
#     Event code 307 (BTN_NORTH)
#     Event code 308 (BTN_WEST)
#     Event code 310 (BTN_TL)
#     Event code 311 (BTN_TR)
#     Event code 314 (BTN_SELECT)
#     Event code 315 (BTN_START)
#     Event code 316 (BTN_MODE)
#     Event code 317 (BTN_THUMBL)
#     Event code 318 (BTN_THUMBR)
#     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 type 3 (EV_ABS)
#     Event code 0 (ABS_X)
#       Value      456
#       Min     -32768
#       Max      32767
#       Fuzz        16
#       Flat       128
#       Resolution   0
#     Event code 1 (ABS_Y)
#       Value      767
#       Min     -32768
#       Max      32767
#       Fuzz        16
#       Flat       128
#       Resolution   0
#     Event code 2 (ABS_Z)
#       Value        0
#       Min          0
#       Max       1023
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 3 (ABS_RX)
#       Value     -717
#       Min     -32768
#       Max      32767
#       Fuzz        16
#       Flat       128
#       Resolution   0
#     Event code 4 (ABS_RY)
#       Value    -1510
#       Min     -32768
#       Max      32767
#       Fuzz        16
#       Flat       128
#       Resolution   0
#     Event code 5 (ABS_RZ)
#       Value        0
#       Min          0
#       Max       1023
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 16 (ABS_HAT0X)
#       Value        0
#       Min         -1
#       Max          1
#       Fuzz         0
#       Flat         0
#       Resolution   0
#     Event code 17 (ABS_HAT0Y)
#       Value        0
#       Min         -1
#       Max          1
#       Fuzz         0
#       Flat         0
#       Resolution   0
#   Event type 21 (EV_FF)
#     Event code 80 (FF_RUMBLE)
#     Event code 81 (FF_PERIODIC)
#     Event code 88 (FF_SQUARE)
#     Event code 89 (FF_TRIANGLE)
#     Event code 90 (FF_SINE)
#     Event code 96 (FF_GAIN)
# Properties:
N: Microsoft X-Box One Elite 2 pad
I: 0003 045e 0b00 0407
P: 00 00 00 00 00 00 00 00
B: 00 0b 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 db 7c
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 f0 00 00 00 00 00 00 00
B: 02 00 00 00 00 00 00 00 00
B: 03 3f 00 03 00 00 00 00 00
B: 04 00 00 00 00 00 00 00 00
B: 05 00 00 00 00 00 00 00 00
B: 11 00 00 00 00 00 00 00 00
B: 12 00 00 00 00 00 00 00 00
B: 14 00 00 00 00 00 00 00 00
B: 15 00 00 00 00 00 00 00 00
B: 15 00 00 03 07 01 00 00 00
A: 00 -32768 32767 16 128 0
A: 01 -32768 32767 16 128 0
A: 02 0 1023 0 0 0
A: 03 -32768 32767 16 128 0
A: 04 -32768 32767 16 128 0
A: 05 0 1023 0 0 0
A: 10 -1 1 0 0 0
A: 11 -1 1 0 0 0

> cat /sys/class/input/event14/device/device/report_descriptor
cat: /sys/class/input/event14/device/device/report_descriptor: No such file or directory

[smcv]

cat: /sys/class/input/event14/device/device/report_descriptor: No such file or directory

This is normal for Xbox controllers connected via USB. They're one of the few common game controllers that uses a vendor-specific protocol instead of USB HID.

[smcv]

This is functionally the same as an Xbox 360 wired USB controller, except that it has four extra buttons (presumably on the back), which for some reason Linux maps to BTN_TRIGGER_HAPPY5 up to BTN_TRIGGER_HAPPY8.

It's unlikely that this will ever be a problem for SDL's gamepad recognition heuristic, which is what is currently tested in testevdev - it has all the buttons and axes of an Xbox 360 controller, and if we break the heuristic badly enough that it stops recognising those, then something has gone very wrong. But I'll put together a PR as a low priority thing.

[smcv]

Is this a wired-only controller, or does it also do Bluetooth? If it can be used via Bluetooth, then the same information for that would be interesting. Over Bluetooth, I would expect that it is a HID device.

[slouken]

This might be interesting for you: atar-axis/xpadneo#428
I filed an upstream issue asking the xpadneo driver folks if there was a way we could automatically detect the share button and paddles so we don't need hand-crafted mappings for every controller.

[smcv]

xpadneo seems to be a third-party, out-of-tree kernel module. Are its maintainers aiming for inclusion in the mainline Linux kernel? I think the modules that are in the Linux kernel should be a higher priority than third-party addons - they're a lot more likely to work without user-specific tweaks - but of course ideally SDL would cope equally well with both.

[smcv]

But I'll put together a PR as a low priority thing

This was #7815 and was merged.

[slouken]

xpadneo seems to be a third-party, out-of-tree kernel module. Are its maintainers aiming for inclusion in the mainline Linux kernel? I think the modules that are in the Linux kernel should be a higher priority than third-party addons - they're a lot more likely to work without user-specific tweaks - but of course ideally SDL would cope equally well with both.

The modules in the Linux kernel have higher priority, but xpadneo is fairly popular and it would be nice if it worked well with SDL out of the box.

[iacore]

I don't even have Bluetooth installed.

Is this a wired-only controller, or does it also do Bluetooth? If it can be used via Bluetooth, then the same information for that would be interesting. Over Bluetooth, I would expect that it is a HID device.

The gamepad device has a Bluetooth mode.

[slouken]

What driver is the kernel using? If you do lsmod | fgrep x, you should see xpad or xone or something like that.

[iacore]

What driver is the kernel using? If you do lsmod | fgrep x, you should see xpad or xone or something like that.

there is xpad

[slouken]

FYI, I've added autodetection support for this controller, and it should work out of the box in the next SDL release (2.28)

Thanks!