macOS: use IORegistryEntryGetRegistryEntryID to resolve paths#322
macOS: use IORegistryEntryGetRegistryEntryID to resolve paths#322
Conversation
With some device connection configurations, the device paths become over 512 bytes (io_string_t max length) which makes them unusable with current implementation. Rather than using ServiceRegistry string path, use its ID, which is uint64_t and easily serializable/deserializable into a string. Implementation idea by felix.schwarz@iospirit.com flirc/hidapi@8d251c3 Fixes: #127, #236.
|
@erikmwerner, @mcuee will you be able to try this out? |
|
This seems to work fine. Without this pull request, it is problematic for my setup whhere I have two powered hub (which are nested hub themselves). |
|
@Youw Is it possible to integrate this patch with the branch https://github.com/libusb/hidapi/tree/get-descriptor? Or what is the simple way for me to merge this patch with my local repo? Sorry I am not good at using git. Or maybe the other way around, integrate get-descriptor branch to the main branch. |
|
Not so sure if the following is the correct way. |
Technically we want to "sync |
With some device connection configurations,
the device paths become over 512 bytes (io_string_t max length)
which makes them unusable with current implementation.
Rather than using ServiceRegistry string path, use its ID,
which is uint64_t and easily serializable/deserializable into a string.
Implementation idea by felix.schwarz@iospirit.com
flirc/hidapi@8d251c3
Fixes: #127, #236.