Fix documentation of lsusb
behaviour
#10903
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.
The documentation did not accurately reflect the behaviour of
lsusb
, which might result in minor confusion.Description
On Fedora 32 (and I assume most other distributions),
lsusb
will display the configuredMANUFACTURER
andPRODUCT
if the database does not contain entries for theVENDOR_ID
andPRODUCT_ID
used. Considering the DB does not contain any entries for the vendor0xFEED
, it should just display the values as advertised by the device.Similarly, doing a
lsusb -v
will not show those values, as it seems that a regular user does not have the required permissions to read them. It will just leave the field empty. Doing asudo lsusb -v
fixes this.Types of Changes
Checklist
Most don't apply because it's just a two-line documentation fix.