Report Interface Number #125
Open
Conversation
This file contains hidden or 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
Closed
…ing forced. Now it is optional in regex
|
would be great to have this merged into the next version |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Many USB devices are composite devices that contain multiple interfaces. If such a device has two or more serial ports (comm ports) then they have the same VID, PID and Serial Number. Because of this, it is currently impossible to distinguish between multiple ports on the same USB composite device. It would be nice to be able to differentiate such devices at the USB level. This patch has the device info return the interface number (MI) in addition to the USB VID and PID.
Tested and works on Window and Linux. I think a very similar change could be done to OSX for this to work on a MAC, but I do not have a MAC to test on.
(New pull request but same content as #124 since #124 is from wrong branch and I will close)