On Sat, Jan 27, 2024 at 12:51 AM Max Staudt <max@xxxxxxxxx> wrote: > > On 1/25/24 09:39, Roderick Colenbrander wrote: > > On Mon, Jan 15, 2024 at 6:58 AM Max Staudt <max@xxxxxxxxx> wrote: > >> > >> Some third-party controllers can't report their MAC address. > >> > > For what type of devices is this not working? This one example of this > > request which is very foundational for a controller working on even > > the game console. Are this perhaps USB-only devices? If the case maybe > > some kind of error is only needed for USB connections. > > IIRC I've only seen this quirk with the oddball VID/PID 7545:0104 that my patch 7/7 adds. It is indeed a USB-only controller. I have not tried this device (or any, really) with an actual console, my focus is just on Linux. Admittedly, I'd also like to know what happens on a real PS4 :) > > My intention was to keep the error message and the solution as universal as possible, in case a controller comes along that has both this quirk *and* Bluetooth. It's a bit of an ugly workaround though - if you (or anyone else) have an idea for a nicer solution, I'd be really glad. > > > Max > I remember on the console side that we support a number of controllers including our official model and some licensed controllers. I recall them taking some different codepaths and HID reports differently. It has been a while, so I don't recall the details. If I remember it could be that all of the licensed ones were USB-only (of course there are some Bluetooth capable clones). For this reason I think not all DS4-compatible devices have a MAC address or handle this request. (We made some fixes in hid-playstation relative to hid-sony, where hid-sony used another less known HID report for the MAC address. Now we use the more commonly known one and that helped other clone devices). I'm not sure about the best way to handle this. I have kind of been leaning towards doing a vid/pid like check for this case even though I really hate it. It could be within dualshock4_get_mac_address as we do some other special handling there too (although having the caller of dualshock4_get_mac_address do it is an option too, but I think within get_mac_address is slightly nicer for now). Thanks, Roderick
