forked from libusb/libusb
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Added libusb_get_device_string() which works with a closed device lib…
…usb#866 This new API call provides access to device strings, normally accessed using USB string descriptors, without opening the device. The common use case is to filter on serial number for selecting one of multiple connected devices. The commit adds the new API function, documentation, and support for the following platforms: * Windows WinUSB * Linux * macOS All platforms support manufacturer, product, and serial number strings. The example/listdevs.c now has a "--verbose" command line argument that prints these strings. Known issues: * On one Ubuntu Linux machine, reading the /sys/bus/usb/ files to get the strings takes a variable amount of time on one device, an xHCI root hub. While the read can be fast, it can also take seconds. Using "cat" at the command line has the exact same behavior. References: * libusb#866 * libusb#875 * libusb#1258 * hjmallon@d0f9fd4 Thank you to the prior work that made this much quicker: * @mcuee * @sonatique * @hjmallon I apologize anyone that I missed. This feature has been in the works for a long time with multiple starts and stops. And thank you to @Youw for providing quick, detailed feedback! Signed-off-by: Matt Liberty <matt.liberty@jetperch.com>
- Loading branch information
Showing
12 changed files
with
439 additions
and
4 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.