You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With hid_darwin_get_location_id (#378) and hid_winapi_get_container_id(#379) we have physical device identifiers for Windows and MacOS, but not for Linux.
The Chromium HID implementation uses the same identifiers for Windows and MacOS, but has also an implementation for hidraw. They use the sysfs path of the device node that represents the physical device as physical identifier. They implemented a recursive search to gather this information: https://chromium.googlesource.com/chromium/src/+/refs/changes/62/3314562/3/services/device/hid/hid_service_linux.cc#138
hidraw:
once we have hid_get_path I believe it is enough to identify the physysical device, since paths like /dev/hidraw* are easily mapped to /sys/class/hidraw/hidraw*; that information should be more than enough for the application to get what it needs;
Activity
Youw commentedon May 18, 2022
once we have
hid_get_pathI believe it is enough to identify the physysical device, since paths like/dev/hidraw*are easily mapped to/sys/class/hidraw/hidraw*; that information should be more than enough for the application to get what it needs;having
hid_get_pathwe may say the very similar thing, as the path we generate (libusb backend: stabilize device path, superseeds: #117 #291) is the same as in/sys/bus/usb/devices/Youw commentedon Aug 21, 2022
Resolved by #432