Update controller-autoconfiguration.md -- The `android`, `udev`, and `sdl2` drivers can use either the Device Index (`input_device`) or a combination of Vendor ID (`input_vendor_id`) and Product ID (`input_product_id`) -- Thanks zoltanvb! #984
The android, udev, and sdl2 drivers can use either the Device Index (input_device) or a combination of Vendor ID (input_vendor_id) and Product ID (input_product_id). If the Device Index is configured incorrectly, the system will fall back on checking the Vendor ID and Product ID, and vice versa. References: input_autoconfigure_get_config_file_affinity in (task_autodetect.c)[https://github.com/libretro/RetroArch/blob/master/tasks/task_autodetect.c], and input_autoconfigure_connect in android_input.c, sdl_joypad.c, udev_joypad.c.
android,udev, andsdl2drivers can use either the Device Index (input_device) or a combination of Vendor ID (input_vendor_id) and Product ID (input_product_id). If the Device Index is configured incorrectly, the system will fall back on checking the Vendor ID and Product ID, and vice versa. References: input_autoconfigure_get_config_file_affinity in (task_autodetect.c)[https://github.com/libretro/RetroArch/blob/master/tasks/task_autodetect.c], andinput_autoconfigure_connectin android_input.c, sdl_joypad.c, udev_joypad.c.