tag 294139 + sarge tag 294139 + sid thanks
Brian Ristuccia wrote:
On Tue, Feb 08, 2005 at 08:38:22PM -0500, Brian Ristuccia wrote:
After some testing, I determined that the combination of usbutils (0.70-1) and libusb-0.1-4 (0.1.9-1) on arm results in bogus zero values for bNumInterfaces and the associated *interface pointer winds up null. This
On further inspection, the entire Configuration Descriptor is zero/empty on arm. Retitled the bug to better summarize the problem. Since libusb is pretty much useless on arm as a result, I'm adjusting the severity also.
Thanks for your very good work, I think I have identified the problem:
When an USB device is plugged, the kernel parses all the descriptors of the device, and make them available in /proc/bus/usb/xxx/xxx. When parsing all the USB devices, libusb first parses this file in /proc and then, if some information are missing, is asking the device directly.
The problem is that in some cases with partial information (ie between no information and full information), libusb doesn't ask the device.
It is not working on your arm computer because the kernel, for an unknown reason, returns partial descriptor.
To answer Steve, the problem it's also in Sarge as this part hasn't changed since version 0.1.7 (sarge has 0.1.8 and sid 0.1.9).
To confirm all what I said, I have produced a test version, which is available on http://temp.aurel32.net/libusb . Could you please test it?
Note that the -dev package for arm doesn't include the doc as jade was not available on the host where I built libusb. Anyway that should not be a problem for the test.
Thanks, Aurelien
-- .''`. Aurelien Jarno GPG: 1024D/F1BCDB73 : :' : Debian GNU/Linux developer | Electrical Engineer `. `' [EMAIL PROTECTED] | [EMAIL PROTECTED] `- people.debian.org/~aurel32 | www.aurel32.net
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
