Hide Forgot
Description of problem: With the inclusion of usb3 (xhci) driver into RHEL-6, the userspace interface has expanded. I would like to bring in the changes to the usbutils to utilize the extra data provided by the xhci driver. Namely the Binary Store Object, which defines usb3 characteristics of the device and more importantly the usb3 hub descriptor, which tells me the status of the usb3 hubs. Because Hub support is a new feature for 6.3, there are growing pains associated with it. It would be easier to debug issues if the userspace piece has changes made to it to display relevant data as opposed to me providing custom kernels. I have cherry-picked a bunch of upstream commits and backported to the RHEL-6 version of usbutils. Once I have finish flushing out some issues, I will attach a tarball of the patches and spec file changes to this bz. I would like to get this into 6.2, but I understand if it is too late. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. lsusb -v 2. notice the garbled data on usb3 devices 3. Actual results: Expected results: Additional info:
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: The usbutils package has been upgraded to upstream version 003, which adds support for USB3 devices.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2011-1646.html