-
-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[IMPORTANT feature request]: Support multiple input_device, input_device_display_name, input_vendor_id, and input_product_id variables #16907
Comments
# The files "Sony Interactive Entertainment Wireless Controller.cfg" and "Wireless Controller.cfg" should have identical content except for the input_device variable until they can be merged when this issue has been solved: [IMPORTANT feature request]: Support multiple input_device names for controller compatibility across Linux kernels - libretro/RetroArch#16907
# The files "Nintendo Co., Ltd. Pro Controller.cfg" and "Nintendo Switch Pro Controller.cfg" should have identical content except for the input_device variable until they can be merged when this issue has been solved: [IMPORTANT feature request]: Support multiple input_device names for controller compatibility across Linux kernels - libretro/RetroArch#16907
# The files "Sony Interactive Entertainment Wireless Controller.cfg" and "Wireless Controller.cfg" should have identical content except for the input_device variable until they can be merged when this issue has been solved: [IMPORTANT feature request]: Support multiple input_device names for controller compatibility across Linux kernels - libretro/RetroArch#16907
It seems more straightforward for a single pull request to remove input_vendor_id from all udev files once we reach a consensus on the issue discussed in: libretro/RetroArch#16907
It seems more straightforward for a single pull request to remove input_vendor_id from all udev files once we reach a consensus on the issue discussed in: libretro/RetroArch#16907
It seems more straightforward for a single pull request to remove input_vendor_id from all udev files once we reach a consensus on the issue discussed in: libretro/RetroArch#16907
It seems more straightforward for a single pull request to remove input_vendor_id from all udev files once we reach a consensus on the issue discussed in: libretro/RetroArch#16907
It seems more straightforward for a single pull request to remove input_vendor_id from all udev files once we reach a consensus on the issue discussed in: libretro/RetroArch#16907
It seems more straightforward for a single pull request to remove input_vendor_id from all udev files once we reach a consensus on the issue discussed in: libretro/RetroArch#16907
It seems more straightforward for a single pull request to remove input_vendor_id from all udev files once we reach a consensus on the issue discussed in: libretro/RetroArch#16907
As discussed in other, related tickets: autoconfig matching is rather flexible, so if the vendor/product ID matches, it will still find the proper autoconfig file, without the need to add multiple names. (This is not valid for the linuxraw driver - that one has no way of knowing vid/pid). There can be limits to this approach, like the one mentioned in #15994 (when not only the name, but also the button layout changes), but that is hopefully a rare occurrence. |
Understood. I've completely rewritten the top post to concentrate on linuxraw. Could you please review it again? |
Avoid input_vendor_id/input_product_id conflict. Support multiple input_device and input_device_display_name variables - libretro/RetroArch#16907
Avoid input_vendor_id/input_product_id conflict. Support multiple input_device and input_device_display_name variables - libretro/RetroArch#16907
Avoid input_vendor_id/input_product_id conflict. Support multiple input_device and input_device_display_name variables - libretro/RetroArch#16907
Avoid input_vendor_id/input_product_id conflict. Support multiple input_device and input_device_display_name variables - libretro/RetroArch#16907
Avoid input_vendor_id/input_product_id conflict. Support multiple input_device and input_device_display_name variables - libretro/RetroArch#16907
Avoid input_vendor_id/input_product_id conflict. Support multiple input_device and input_device_display_name variables - libretro/RetroArch#16907
Checked, makes sense. |
|
input_device (linuxraw)
To avoid the need for uploading and maintaining multiple copies of files for
linuxraw
, which usesinput_device
to identify the controller, I propose the following:input_device_alt1
andinput_device_display_name_alt1
input_device_alt2
andinput_device_display_name_alt2
After implementation, this can be incorporated into the
android
andudev
autoconfiguration files as well, to significantly enhance their ability to utilize input_device as fallback when the vendor or product ID is unavailable. This feature is unnecessary forsdl2
autoconfig files because they use the same input_device value for both USB and Bluetooth across all Linux kernel versions.Placed USB lines before Bluetooth lines in the examples below, as the input_device USB name more clearly identifies the hardware device.
Nintendo Switch Pro Controller
Current
Nintendo Switch Pro Controller.cfg
Nintendo Co., Ltd. Pro Controller.cfg
Pro Controller.cfg
Proposed merge
Nintendo Switch Pro Controller.cfg
Nintendo Switch Pro Controller (non-HID)
Notes:
Sony DualSense
Current
Sony Interactive Entertainment DualSense Wireless Controller.cfg
DualSense Wireless Controller.cfg
Proposed merge
Sony Interactive Entertainment DualSense Wireless Controller.cfg
Sony DualShock 4 v2
Current
Sony Interactive Entertainment Wireless Controller.cfg
Wireless Controller.cfg
Proposed merge
Sony Interactive Entertainment Wireless Controller.cfg
input_vendor_id, and input_product_id (android, udev, sdl2)
input_vendor_id_alt1
andinput_vendor_product_alt1
so we can:DualShock 4 v1 and v2
android
Merge
Sony Computer Entertainment Wireless Controller.cfg
(v1) andWireless Controller.cfg
(v2)Current
DualShock 4 v1:
Sony Computer Entertainment Wireless Controller.cfg
DualShock 4 v2:
Wireless Controller.cfg
Proposed merge
DualShock 4.cfg
sdl2
Merge
PS4 Controller (v1).cfg
(v1) andPS4 Controller.cfg
(v2)Current
DualShock 4 v1:
PS4 Controller (v1).cfg
DualShock 4 v2:
PS4 Controller.cfg
Proposed merge
PS4 Controller.cfg
udev
Merge
Sony Computer Entertainment Wireless Controller.cfg
(v1) andSony Interactive Entertainment Wireless Controller.cfg
(v2)Current
DualShock 4 v1:
Sony Computer Entertainment Wireless Controller.cfg
DualShock 4 v2:
Sony Interactive Entertainment Wireless Controller.cfg
Proposed merge
Sony Computer and Interactive Entertainment Wireless Controller.cfg
The text was updated successfully, but these errors were encountered: