libusb 1.0+0.1 resync from master as of 2021-12-21 #1234
Merged
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
Signed-off-by: Mauro Guerrera <[email protected]>
Signed-off-by: Mauro Guerrera <[email protected]>
Clarify SNMP auth/priv proto support depends on Net-SNMP lib
Clarify SNMP auth/priv proto support depends on Net-SNMP lib
…I farm tells how to reproduce builds
…d_to_only_catch_errors()
At least one UPS [APC Back-UPS BX1600MI FW:294201G -302201G] is known to have encoding errors in its USB HID report description such that a conforming interpretation of the encoded LogicalMaximum value indicates that it is -1 and the resulting LogicalMin..LogicalMax range is 0..-1. The actual report values read are correctly encoded. Rather than log a range error each time a value is read we can detect the encoding error when the report description is read (once, at startup) and adjust for the encoding error at that time.
For some devices, missing instcmds are emulated by calling two instcmds that do exist in sequence. For some devices, when these commands arrive too quickly, they are not properly processed. (One, both, or neither of the commands are acted upon.) Adding a 1/8th-second delay (125,000 microseconds) between the two instcmds that make up the fallback command has worked to make the TrippLite AVR750U (new version with the 3024 productId/protocol) behave consistently when using the fallback commands (shutdown.return and shutdown.stayoff). This delay is also short enough that it seems unlikely to cause a problem for any devices which don't exhibit this issue.
Fix whitespace in recent changes for LogMin/LogMax rectification
…interpretation
Older compilers complain that we are:
passing argument 3 of 'usb_interrupt_read' from incompatible pointer type
expected 'char *' but argument is of type 'char (*)[512]'
Add VID/PID for Minuteman UPS
…d scenarios, they are too noisy in fightwarn for no real good
…ys, but without "pedantic" for C89/C90/ANSI builds (flaws in OS headers are out of our control)
…gs without "pedantic" for C89/C90/ANSI builds (flaws in OS headers are out of our control)
… type conversions
…arning (overkill the buffer size a bit)
…_item_buffered(): fix "age" from int to time_t, to match time() operations
…ault-all-errors processing
… a separate NUT_SSL_VARIANTS=auto
jimklimov
added
USB
CI
…ault-all-errors processing (extend to libusb-1.0* branches)
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.
Bringing libusb-1.0 and libusb-1.0+0.1 branches to another level of common baseline, to simplify subsequent PRs for eventual merge of the feature to master for #300.
Note: For finishing touches, https://github.com/networkupstools/nut/tree/fightwarn-libusb-1.0+0.1 will be merged into this target branch next.