| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|\
| |
| | |
lsusb: decode CDC MBIM descriptor
|
|/
|
|
|
|
| |
Adding support for the CDC MBIM functional descriptor.
Signed-off-by: Bjørn Mork <bjorn@mork.no>
|
| |
|
| |
|
|
|
|
| |
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
| |
This fixes the annoying "bInterfaceClass 0x0e not yet handled" messages
in 'lsusb -t' for video devices, and will handle any future class types
as well.
Just one step in merging 'lsusb -t' into the main portion of the program
instead of really just being a stand-alone program.
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
|
|
|
|
|
|
|
| |
It wasn't doing anything, and I don't know what it ever did, so remove
it. It also wasn't documented, so hopefully will not break anyone's
scripts...
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The original code to print bmAttributes had the meaning of the LTM bit
backwards. The USB 3.0 spec, section 9.6.2.2, says that bit 1 means:
"LTM Capable. A value of one in this bit location indicates that this
device has is capable of generating Latency Tolerance Messages."
Only print LTM supported if bit 1 is set.
Signed-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Get Status value for USB 3.0 devices adds three new status bits.
Bits 2 and 3 indicate if U1 and U2 are enabled, and bit 4 indicates if
Latency Tolerance Messaging (LTM) is enabled.
Upcoming patches for the Linux kernel will enable LTM, so lsusb should
be changed to show whether LTM is enabled for a device.
Signed-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
|
|
|
|
| |
Signed-off-by: Aurelien Jarno <aurelien@aurel32.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
|\
| |
| | |
Minor issue: lsusb -V should not take a argument
|
|/
|
|
| |
Signed-off-by: Roger Tseng <rogerable@realtek.com>
|
| |
|
|\
| |
| | |
Patch reworked
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Update usbhid-dump to complete 1.3 release. Previous update was to
incomplete release, missing two last changes.
This release adds several build fixes, manual page and an infinite loop fix
in command-line option parsing on unsigned char platforms.
Signed-off-by: Nikolai Kondrashov <spbnick@gmail.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
|
|\ \
| |/
|/| |
Allow disabling usb.ids (and script) install.
|
|/
|
|
|
|
|
| |
Also avoid installing update-usbids.sh script if we're not going to
install usb.ids. This is useful for Gentoo since we now have a
separate package for usb.ids, which can be updated independently, and
that can be updated without this script.
|
|
|
|
|
|
|
|
| |
treedump() doesn't require neither names nor libusb so
it's a shame to abort in case we failed to parse usb.ids or
to initialize libusb...
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|
|
|
| |
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|
|
|
|
|
|
|
|
|
|
| |
USB devices with a BCD of 0x0201 or greater will have a USB 2.0
extension BOS descriptor. They may also have a SuperSpeed Capabilities
BOS descriptor, which indicates a USB 3.0 device has been plugged into a
USB 2.0 only port. Make lsusb display all BOS descriptors for USB 2.01
devices and later.
Signed-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|
|
|
|
|
| |
(free_*) fix segfaulting when calling usb_probe() more than once
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|
|
|
|
|
|
|
| |
Because readlink() does not null-terminate buffer, only return
number of written chars, thare is possibility that buf[ret] = 0;
will write to unallocated area.
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|
|
|
|
|
|
| |
In previouse version ((buf[7] << 4) & 3) was always zero.
Since we are interested in bits 4 and 5 there should be >> operator.
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|
|
|
|
|
|
|
| |
If (!pn || p == pn) is true function returns
and memory allocated few lines earlier will
be lost.
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|
|
|
|
|
| |
Variable 'k' was not initialize before it's usage here.
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|
|
|
|
|
|
| |
Walking through array chconfig (of size only 12 items)
by for loop with stop-value 26.
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|
|
|
|
|
|
| |
Macro SYSFS_STR was set to read MY_SYSFS_FILENAME_LEN (255) chars
but size of arrays is only 64.
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|\ |
|
| | |
|
| |
| |
| |
| | |
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
| |
| |
| |
| | |
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
| |
| |
| |
| | |
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I want to suggest adding one more space between version and speed in
lsusb.py. For USB 3.0 devices are these numbers connected.
Example:
3-4.1.2 090c:1000 00 2.00 480MBit/s 100mA 1IFs (SMI Corporation USB DISK AA04012700009416)
usb4 1d6b:0003 09 3.005000MBit/s 0mA 1IFs (xhci_hcd 0000:00:14.0)
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
| | |
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The bU2DevExitLat field is a 2 byte field. According to the USB 3.0
specification, all mult-byte fields are moved over the bus in little-endian
order (least significant byte first). So buf[8] is the LSB, buf[9] is the MSB
of the U2 exit latency value.
Signed-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The wSpeedsSupported field in the SuperSpeed Device Capabilities descriptor in
the BOS descriptor is two bytes wide, not one byte. Shift all the following
reads of the buffer by one byte.
Signed-off-by: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
This keeps us from having to track the movements of them, as that's a
pointless exercise.
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|/ |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Am 25.05.2011 00:18 schrieb Greg KH:
> On Wed, May 25, 2011 at 12:02:48AM +0200, Carl-Daniel Hailfinger wrote:
>
>> I was playing with the "authorized" attribute of USB devices in
>> sysfs.
>> If at least one device has authorized=0,
>> "lsusb" will print nothing (not even the host controllers)
>>
> Well, if the device can't be accessed, as you disabled it through the
> authorised=0 setting, lsusb shouldn't really be able to do much with it.
>
Turns out there are two bugs:
libusb screws up walking the bus and claims there are -1 devices (error).
lsusb ignores that and tries to free a nonexisting object.
Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|
|
|
|
|
|
|
|
|
| |
If read_sysfs_file_string() encounters a zero-length file, it will write
'\0' at index -1 of the provided buffer. Handle zero-length files
gracefully by falling through to the error handler which does the right
thing (tm).
Signed-off-by: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
|
|\
| |
| | |
Verbose flag in tree mode shows vendor and product name.
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
When running `lsusb -tv`, devices should have the vendor and
product name appended to the row.
Signed-off-by: Dafydd Crosby <dtcrsby@gmail.com>
|
|\ \
| | |
| | | |
don't use invalid config descriptors
|
|/ /
| |
| |
| |
| | |
This fixes "lsusb -v" crashing if device files are present but can't be
opened.
|