fix: Motorola adbfast code, also sort codes and use default drop #297
Conversation
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
Fixed typing error with adbfast in issue 293 and 296. Sorted several codes numerically and added some more adb related codes scrapped from libmtp idProduct values. Higher confidence due to idProduct values given in issue 296, therefore converted Motorola from blanket accept to default drop.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 issue #293 and issue #296 for fastboot.
Thanks to @icyrockcom and @fuyukihidekii
Also tidy-up some vendor values, and convert the Motorola section from default accept everything to default drop unknown codes. Non-adb related vendor codes drops through, to be surrendered to other USB rules.