proc_usb_info.txt: Correct documentation about endianness of config descriptors
The config descriptors as read from /proc/bus/usb/BBB/DDD are in *bus* endian format. Correct proc_usb_info.txt to correctly reflect that. Signed-off-by: Hans de Goede <hdegoede@redhat.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
This commit is contained in:
parent
b4f17a488a
commit
21a9631586
|
@ -54,9 +54,12 @@ it and 002/048 sometime later.
|
||||||
|
|
||||||
These files can be read as binary data. The binary data consists
|
These files can be read as binary data. The binary data consists
|
||||||
of first the device descriptor, then the descriptors for each
|
of first the device descriptor, then the descriptors for each
|
||||||
configuration of the device. Multi-byte fields in the device and
|
configuration of the device. Multi-byte fields in the device descriptor
|
||||||
configuration descriptors, but not other descriptors, are converted
|
are converted to host endianness by the kernel. The configuration
|
||||||
to host endianness by the kernel. This information is also shown
|
descriptors are in bus endian format! The configuration descriptor
|
||||||
|
are wTotalLength bytes apart. If a device returns less configuration
|
||||||
|
descriptor data than indicated by wTotalLength there will be a hole in
|
||||||
|
the file for the missing bytes. This information is also shown
|
||||||
in text form by the /proc/bus/usb/devices file, described later.
|
in text form by the /proc/bus/usb/devices file, described later.
|
||||||
|
|
||||||
These files may also be used to write user-level drivers for the USB
|
These files may also be used to write user-level drivers for the USB
|
||||||
|
|
Loading…
Reference in New Issue