https://bugs.winehq.org/show_bug.cgi?id=52462
--- Comment #5 from Josesk Volpe joseskvolpe@gmail.com --- By looking deep in the code and Windows documentations, i guess this conception
however on Windows gamepad drivers has to map their buttons to XInput as a Xbox controller >regardless it's a Xbox, PlayStation, Nintendo or a Generic controller.
Is much probably very wrong ¿maybe? I would like to know, still learning :3
Anyways, Wine has implemented a library to detect if a device is a gamepad, on unixlib.c, there's the functions:
BOOL is_xbox_gamepad(WORD vid, WORD pid) BOOL is_dualshock4_gamepad(WORD vid, WORD pid) BOOL is_dualsense_gamepad(WORD vid, WORD pid)
And other functions to identify other kind of devices such as mouse and keyboard. On these 3 specified functions, Wine lists many VID and PID for known devices. But VID 0x1949 PID 0x402 aren't listed. However, looking by tracing functions, handle_DeviceMatchingCallback from bus_iohid.c isn't invoked when starting Wine, ´wine control´'s gamepad settings and testing the gamepad from there. So i'm not sure it matters at all on this case.
¿Should i go to Windows and look into how this gamepad works with the generic gamepad driver to view what keycodes does it receive from the driver?