Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

testevdev: Add some driving sim controllers from Proton issue reports #7598

Merged
merged 2 commits into from
May 23, 2023

Conversation

smcv
Copy link
Contributor

@smcv smcv commented Apr 11, 2023

Description

  • testevdev: Add the ability to mark a device entry as unimplemented

    There are some devices for which SDL's device classification heuristic
    is known not to give the ideal result. Add a way to incorporate these
    into our test data, so that when the heuristic is improved we can
    detect them as their intended device type, without making the test fail
    before that has been implemented.

  • testevdev: Add some driving sim controllers from Proton issue reports

    Ideally we'd detect these as "joysticks" (or more generally, gaming
    controllers), but in most cases their evdev flags are indistinguishable
    from an accelerometer or gyro, so the only way to achieve this would be
    a table of known devices that doesn't currently exist.

    One exception is the one that reports a THROTTLE axis and TRIGGER, THUMB
    buttons, which would be reasonable to detect via the joystick heuristic.

Existing Issue(s)

Related to #7500, #7501. I don't currently have steam-runtime-input-monitor or evemu-describe output for the device that issue report describes, so I can't add it here, but it would be good to add that device as well.

There are some devices for which SDL's device classification heuristic
is known not to give the ideal result. Add a way to incorporate these
into our test data, so that when the heuristic is improved we can
detect them as their intended device type, without making the test fail
before that has been implemented.

Signed-off-by: Simon McVittie <smcv@collabora.com>
Ideally we'd detect these as "joysticks" (or more generally, gaming
controllers), but in most cases their evdev flags are indistinguishable
from an accelerometer or gyro, so the only way to achieve this would be
a table of known devices that doesn't currently exist.

One exception is the one that reports a THROTTLE axis and TRIGGER, THUMB
buttons, which would be reasonable to detect via the joystick heuristic.

Signed-off-by: Simon McVittie <smcv@collabora.com>
Comment on lines +946 to +950
.name = "Smarty Co. VRS DirectForce Pro Pedals",
.bus_type = 0x0003,
.vendor_id = 0x0483, /* STMicroelectronics */
.product_id = 0xa3be, /* VRS DirectForce Pro Pedals */
.version = 0x0111,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This appears to be https://virtualracingschool.com/dfpro-pedals/, presumably a smaller manufacturer using a ST Microelectronics USB component and borrowing ST Microelectronics' vendor ID - hopefully with permission, but who knows.

Comment on lines +998 to +1002
.name = "Leo Bodnar Logitech® G25 Pedals",
.bus_type = 0x0003,
.vendor_id = 0x1dd2, /* Leo Bodnar Electronics Ltd */
.product_id = 0x100c,
.version = 0x0110,
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This appears to be https://www.leobodnar.com/shop/index.php?main_page=product_info&products_id=187, a third-party serial-to-USB adapter to connect Logitech G25 pedals (only) as a separate game controller.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants