add lsusb.py to the bin files

This should get it installed properly.

Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Merge branch 'Flameeyes-master'

* Flameeyes-master:
  Print device class descriptors like it's done for interface descriptors.
  Simplify the configure script.
usbutils 002 release
build-sys: properly enable support for zlib in lsusb

Define HAVE_LIBZ to enable the code and append -lz to the linking line.

Cc: Gabor Z. Papp <gzp@papp.hu>

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>
usbutils 003 release
Fix compiler warning
don't use invalid config descriptors

This fixes "lsusb -v" crashing if device files are present but can't be
opened.
Merge pull request #2 from nphilipp/master--nphilipp

don't use invalid config descriptors
Merge pull request #3 from dafyddcrosby/lsusb-tv

Verbose flag in tree mode shows vendor and product name.
Fix lsusb out-of-bounds write

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>
Fix lsusb double-free

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>
usbutils 004 release
usb.ids: updated version of the file
Remove the FSF address from the source files.

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>
update usbhid-dump to release 1.2
lsusb: wSpeedsSupported is 2 bytes, not one.

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>
lsusb: bU2DevExitLat is little endian, not big endian.

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>
add another Linux kernel usb id.
Add more space to lsusb.py output

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>