Re: [Libusbx-devel] [libusbx] persisting LIBUSB_ERROR_NO_MEM on burst condition

2013-01-30 Thread Pete Batard
On 2013.01.30 20:43, Mohamed HAMZAOUI wrote: > Does the number of handling event call should be equal or great the > number of transfer submitting given that the handler thread execute > the callback and then spent more time on executing them ? I'm not sure I understand your question, but I don't

Re: [Libusbx-devel] [libusbx] persisting LIBUSB_ERROR_NO_MEM on burst condition

2013-01-30 Thread Mohamed HAMZAOUI
I have an important inforation, I added a hanling event instruction on sender thread just after sending, so, we have one thread for handling and another thread for sending and handling an event after sending and i protect the two handling call with libusb_lock/unlock_event function like that : /***

Re: [Libusbx-devel] [libusbx] persisting LIBUSB_ERROR_NO_MEM on burst condition

2013-01-30 Thread Mohamed HAMZAOUI
On Wed, Jan 30, 2013 at 6:33 AM, Xiaofan Chen wrote: > On Wed, Jan 30, 2013 at 12:45 AM, Mohamed HAMZAOUI > wrote: >> Now I use libusbx library static in debug mode (i just have changed >> /MTd to /MDd in compiling parameter). >> >> more information about the bug : there is a corruption in memor

Re: [Libusbx-devel] Issue #72 libusb0.sys filter and USB composite device

2013-01-30 Thread Xiaofan Chen
On Wed, Jan 30, 2013 at 11:01 PM, Xiaofan Chen wrote: > Just a note here. > > I've created ticket #72 and put some test logs in the ticket. > https://github.com/libusbx/libusbx/issues/72 > > The reason I start to test this one is because that some > people in OpenOCD would like to get the filter d

[Libusbx-devel] Issue #72 libusb0.sys filter and USB composite device

2013-01-30 Thread Xiaofan Chen
Just a note here. I've created ticket #72 and put some test logs in the ticket. https://github.com/libusbx/libusbx/issues/72 The reason I start to test this one is because that some people in OpenOCD would like to get the filter driver to work with FT2232x (USB composite device) so that they can