motolav

> Do you know if the device is compatible with XBox? Can you post a link to the exact product page? @berarma There's different 3 different SKUs for Xbox/PC, PlayStation/PC,...

change to hid-ids.h ``` #define USB_DEVICE_ID_LOGITECH_G_PRO_RACING_XBOX_WHEEL 0xc272 ``` change to hid-logitech-hidpp.c ``` { /* Logitech G Pro Racing Wheel over USB (Xbox version) */ HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_LOGITECH_G_PRO_RACING_XBOX_WHEEL), .driver_data = HIDPP_QUIRK_CLASS_G920 |...

That has a different ID, idProduct=c26e, so it wouldn't work with my repo yet the ID c26e matches the G923 so maybe its in G923 mode?

Somewhere in `.driver_data = HIDPP_QUIRK_CLASS_G920` it's probably initializing the wheel into G923 mode so the G pro would need different code to start in the native mode since it's masking...

the analog padals are lost but it since the driver loaded and set the wheel into G923 mode it is HID++ and I think I figured out what caused it...

`HIDPP_QUIRK_CLASS_G920` has a block of code within the function `hidpp_input_mapped` so probably all axis need to be included but the G Pro will need a different quirk from the G920....

It's breaking at the `hidpp_ff_init` inside `hidpp_probe` ``` ... } else if (connected && (hidpp->quirks & HIDPP_QUIRK_CLASS_G920)) { ret = g920_get_config(hidpp, &data); if (ret) goto hid_hw_init_fail; } hidpp_connect_event(hidpp); ... if...

Yeah the G920 code likely isn't compatible at all if I'm reading that log right since there's 3 different devices (hidpp_report: 16, hidpp_report: 17, hidpp_report: 18) Did you have the...

I'd try plugging the pedals directly into a computer to see if they have their own USB ID, if they do then my theory of the base being a Unifying...

> Doesn't the most recent G923 patch help? The Xbox G923 is identical to the Xbox G920 software wise so all it needed was the USB IDs defined