Handling of different remotes with same input_vendor_id and input_product_id

[fekir]

Hello, I wanted to try Lakka out, but found a (for me) blocking issue.

Unfortunately I have a remote that has a input_vendor_id and input_product_id that clashes with other remotes (see libretro/retroarch-joypad-autoconfig#1202)

This leads to the situation that my remote is recognized incorrectly.

The workaround in retroarch, when installed as normal application, is to remove the udev files of the other remotes.

In Lakka (at least when installed on the raspberry) there is no autoconfig/udev folder, thus I see no way to remove the offending files.

1. Shortterm solution

can I somehow remove the autoconfig settings for the remotes I do not have, so that my remote has a unique input_vendor_id / input_product_id?

2. Longterm solution

I'm not sure if this has already been discussed.

Lakka should probably ask me what remote I actually have if the remote does not have a uniqueinput_vendor_id/input_product_id`.
Although it might get tricky to make a dialog that works with all three remotes (in this case: iNNEXT SNES, Hyperkin Sega Genesis Controller, and Retrolink Sega Saturn USB GamePad) I think it should be doable.
AFAIK the arrows work on all three consistently, thus navigation should not be an issue.
The dialog could probably say "To select, press A if on remote X, press B on remote Y, ...".

[gouchi]

Hi,

There is a new feature with this PR "Extend autoconfig matching with a physical identifier" . I think it could help your case.

It will be available in next nightly build when it is ready.

Thank you.

[fekir]

Hi @gouchi , thank you for the heads up.

Although I do not understand what I should do to make my controller work out of the box; libretro/RetroArch#18190 says that

[...] can be added to the autoconfig file to direct the match to a different config with same vid/pid/name, but matching phys value.

[gouchi]

Hi @fekir, IIUC you will need to modify the joypad autoconfig file by adding

input_phys = "XXX"

You can get the information by running RA in debug log and should look for

[DEBUG] [Autoconf] Config files scanned: driver udev

Otherwise, you can do something like this

# Get the event path for your controller
for ev in /dev/input/event*; do echo -n "$ev: "; cat /sys/class/input/$(basename $ev)/device/name; done

# Then use it to get the attribute
udevadm info -a -n /dev/input/eventX | grep -E '\bphys\b|uniq'