Fix hang on GIGABYTE keyboard #41
Merged
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.
resolves #40
0 length items in the configuration descriptor.
As I mentioned in the issue: There as some devices who have 0 length fields within their configuration descriptor
Example GIGABYTE keyboard.
The issue came up before on another USBHost library (USBHost_t36).
The solution is when you find a zero length field, you simply increment to the next byte.
It works on my WIP branch, however here hard to test as the current released code fails to read in the full descriptors.
But that is a different issue and PR.