Hi,

I'm not sure, but this seems same problem I had before, see
https://github.com/libusbx/libusbx/commit/2f5023c41d3176e56bf0abc521b7c5f8b1ac4664

Zoltan

2013/2/11 Dominik Röttsches <d...@roettsches.de>:
> Hi Xiaofan,
>
> thanks very much for commenting.
>
> Xiaofan Chen 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?
>
>> You may want to follow that post to see if the new driver (hopefully
>> be integrated into main line kernel in a few iterations) can help
>> to sort out the issues.
>
> Thanks for the pointer, I will try to reach out to Paul Zimmermann
> about this effort.
>
> Dominik
>
>
>
>
> ------------------------------------------------------------------------------
> 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

------------------------------------------------------------------------------
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

Reply via email to