Bug 195225
Summary: | Dualshock controllers have different names when it is connected with USB and bluetooth | ||
---|---|---|---|
Product: | Drivers | Reporter: | haakobja |
Component: | Input Devices | Assignee: | drivers_input-devices |
Status: | NEW --- | ||
Severity: | normal | CC: | nicolas.werner, thunderbird2k |
Priority: | P1 | ||
Hardware: | All | ||
OS: | Linux | ||
Kernel Version: | 4.10.6 | Subsystem: | |
Regression: | No | Bisected commit-id: | |
Attachments: | bluez patch for sixaxis |
Description
haakobja
2017-04-02 15:05:12 UTC
Created attachment 257819 [details]
bluez patch for sixaxis
I had the same problem with my Dual Shock 3. I actually wrote a patch that fixes this issue and sent it to the bluez mailing list, but I got no responses. Maybe I should poke them again...
At least in the USB case (need trace BT kernel path) the device strings just come from the device. Applications typically don't use (and should not use) strings, but instead use hardware device ids. In case of steam in early 2017, I'm not sure if they handled the new ds4 model yet and maybe because of that fell back to strings, but that's just a guess. |