On Mon, Feb 11, 2013 at 11:48 PM, Dominik Röttsches <d...@roettsches.de> wrote: >>> There seems to be an issue with the communication >>> between libusbx and the Rasperry's USB stack. >> >> The bug seems to be specific to Raspberry Pi so I think >> we can not help you much. > > I'd agree it does. But would you have any idea what's the underlying > cause? Any suspicion what might be going on in the driver - anything you > could guess from the straces?
https://github.com/raspberrypi/linux/issues/79 LIBUSB_ERROR_TIMEOUT = -7 "It depends how the code handles errors. I have found libusb_interrupt_transfer reads on other hardware can return a timeout but actually has transferred the data so a timeout might not 'really' be a timeout. On RPi however the returned data is simply missing some of the time." That is the key. As per the thread (the USB HW Analyzer should definitely help the analysis), the data is on the USB Bus. Please check if there are errors on the USB Bus, eg, data toggle error. So suggestions. 1) Try latest git version of libusbx. 2) Try latest kernel available for your platform. 3) Use the USB HW Ananlyzer (or kernel usbmon if it is not available to you) to capture the data of good system (standard Linux system) and bad system (Rasperry Pi). -- Xiaofan ------------------------------------------------------------------------------ Free Next-Gen Firewall Hardware Offer Buy your Sophos next-gen firewall before the end March 2013 and get the hardware for free! Learn more. http://p.sf.net/sfu/sophos-d2d-feb _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
