dogtopus

Sure. I updated the "HID descriptor" gist to include the `lsusb -vd` output.

> Did you actually try serialusb between the Dualsense and a Windows PC? As serialusb stalls device qualifier descriptor requests, it is actually able to force the communication to go...

There's a weird 64-bit checksum-y field located at the end of each input report and I can't figure out how it's calculated. It doesn't seem to be one of the...

@matlo It's practically impossible to get the same report twice since there are timestamps involved.

I changed my fuzzing technique to be more aggressive and automated (i.e. throwing random bits and see what turns what on) and made some progress on the output report format.

Some update on the bluetooth side of the checksum (last **4** bytes): > The crc32-esque thing is just standard crc32 with custom initial value 0x23fcc4d3 and without flipping all the...

Just saw some real protocol captures from others: the auth sequence seems indeed very different compare to DS4 but looks like it should still be passthrough-able. Might need more confirmations....

> Somewhat good news as PS5 supports DS4 I've tried GIMX DS4 BT mode connecting from PC to console over bluetooth works with PS5 > I assume wired connection would...

> Not sure someone is interested, but there are some info I found: > > 1. DualSense works fine in USB FS mode if no data was tampered > 2....

> Isn't Bluetooth report use plain CRC as you mentioned and discovered earlier? Before the CRC field there's also the 64-bit MAC/checksum stuff. > 64 bit checksum doesn't make much...