Wireshark-bugs: [Wireshark-bugs] [Bug 7933] Add ability to reverse FT_BYTES for display
Comment # 8
on bug 7933
from Steve Magnani
The two cases I have in USB Video are:
- A device control (property) whose value can be any device-defined length.
Standard controls for things like brightness have integral values and can be
represented with the standard FT_UINT types. But there are vendor-specific
controls that have "odd" lengths, such as one from Logitech that is 5 bytes
and another that is 32. These are likely not intended to be interpreted as
integers, but as they are vendor-specific it's impossible to know. All we can
go on is the USB requirement that multi-byte values be sent with
little-endian
ordering.
Reference: frames 90 and 262 of
https://bugs.wireshark.org/bugzilla/attachment.cgi?id=10160
- A bitmask whose value can be any device-defined length. This is similar
to the first case, but the value clearly makes more sense in hex than
decimal.
Here there is an issue not only of "odd" length, but lengths that are beyond
the ability of the current Wireshark bitmask dissection infrastructure to
display (> 4 bytes).
You are receiving this mail because:
- You are watching all bug changes.
