Re: [Libusbx-devel] libusb_set_configuration() function hangs

So in that case, with this new release which I got through http://libusb.info/ what are the compatible drivers? Best Regards, Pradeepa Senanayake. On Fri, Jan 10, 2014 at 12:43 PM, Xiaofan Chen wrote: > On Fri, Jan 10, 2014 at 3:12 PM, Xiaofan Chen wrote: > > On Fri, Jan 10, 2014 at 2:17 PM,

Re: [Libusbx-devel] libusb_set_configuration() function hangs

On Fri, Jan 10, 2014 at 3:12 PM, Xiaofan Chen wrote: > On Fri, Jan 10, 2014 at 2:17 PM, Pradeepa Senanayake > wrote: >> Hello all, >> >> I have an application using libusb-win32 API and a device using libusb0.sys >> driver. I wanted to check the possibility of using the newly released libusb >> l

Re: [Libusbx-devel] libusb_set_configuration() function hangs

no i did not change. Best Regards, Pradeepa Senanayake. On Fri, Jan 10, 2014 at 12:42 PM, Xiaofan Chen wrote: > On Fri, Jan 10, 2014 at 2:17 PM, Pradeepa Senanayake > wrote: > > Hello all, > > > > I have an application using libusb-win32 API and a device using > libusb0.sys > > driver. I want

Re: [Libusbx-devel] libusb_set_configuration() function hangs

On Fri, Jan 10, 2014 at 2:17 PM, Pradeepa Senanayake wrote: > Hello all, > > I have an application using libusb-win32 API and a device using libusb0.sys > driver. I wanted to check the possibility of using the newly released libusb > library in my application. So I just tried to open the device an

Re: [Libusbx-devel] [libusbx] Core: libusb_interrupt_transfer and libusb_control_transfer does not return in case of error (#76)

If an EFAULT return from the kernel results in an infinite loop in libusb(x): It's not a matter of _recovering_ from the EFAULT. It's a matter of whether libusb(x) should propagate it to the caller or not. There is simply _no_ excuse not to propagate it. Should we tell the kernel developers no

[Libusbx-devel] libusb_set_configuration() function hangs

Hello all, I have an application using libusb-win32 API and a device using libusb0.sys driver. I wanted to check the possibility of using the newly released libusb library in my application. So I just tried to open the device and set the configurations. The API can correctly identify the device,

Re: [Libusbx-devel] [libusbx] break from never ending loop. fix #76. (#167)

Hi Pete, for me it is fairly easy to reproduce with an ultrasound equipment we developed in PUC-Rio university using Opalkelly FPGA cards (which include USB ports). I can run our app + libusbx receiving tons of data for days flawless if the highvoltage ultrasound power supply is disabled. Howe

Re: [Libusbx-devel] [PATCH] Fix example hotplug code in comment to make it compile and work

Unless we find something critical, I STRONGLY vote to delay it until after 1.0.18, even if it's doc. As Murphy's day (yesterday) taught me, if there's anything that can go wrong when duplicating work, it will go wrong. The github sudden breakage [1], which you are aware of, and which thankfully ha

Re: [Libusbx-devel] [libusbx] break from never ending loop. fix #76. (#167)

Thanks for the patch. We'll see what we can do to integrate it, but can you tell us a bit more about the circumstances where this behaviour occurs, and how easy or difficult it is to produce (i.e. do you see the infinite loop consistently happening in an app, or is it a bit more random)? /Pete

Re: [Libusbx-devel] [PATCH] Fix example hotplug code in comment to make it compile and work

Hello, Now the merge is on a good track it may be time to fix minor things like the documentation as proposed in this "old" patch. Or should we wait after the 1.0.18 is released? Bye 2013/12/20 Markus Heidelberg : > Also add #include directives since this is a complete program including > main()

[Libusbx-devel] [libusbx] break from never ending loop. fix #76. (#167)

exit from sync_transfer_wait_for_completion when libusb_handle_events_completed failed and libusb_cancel_transfer returns LIBUSB_ERROR_NOT_FOUND. this error is returned when urbs is not found in kernel (it was already dequeued from async_completed list), therefore there is nothing to cancel. if w

Re: [Libusbx-devel] Announcing libusb-1.0.18-rc1

Hi Joshua, On 2014.01.09 19:57, Joshua Blake wrote: > Change there -> here, since this is read on the new site (rather than an > email referencing it.) This will eliminate confusion about whether > you're referencing "this" site here (libusb.info ) > or the old site. Good poin

Re: [Libusbx-devel] Announcing libusb-1.0.18-rc1

On Thu, Jan 9, 2014 at 2:41 PM, Pete Batard wrote: > libusb.info > Pete, First congrats on the merge. Small suggestion on this the new site: What happened to the old site? The old site is now obsolete. Please use *libusb.info *. All of the libusb development has moved th

Re: [Libusbx-devel] Announcing libusb-1.0.18-rc1

On 2014.01.09 06:30, Bent Bisballe Nyeng wrote: > How much difference will there be to libusbx-1.0.18 and libusb-1.0.18? As far as developers are concerned, no difference. > What I mean is; will the merge simply be a copy of the current libusbx > code to the libusb repository Yup. Just one extra

Re: [Libusbx-devel] [libusbx] Core: libusb_interrupt_transfer and libusb_control_transfer does not return in case of error (#76)

How may I prove you that I'm not providing invalid buffers to libusb? 1) I have already added code to libusb to read and rewrite every byte of the provided buffer. So if it was a bad pointer case it would certainly have crashed. 2) The same code runs for days flawless if I just disable the hig

Re: [Libusbx-devel] [libusbx] Core: libusb_interrupt_transfer and libusb_control_transfer does not return in case of error (#76)

miguelfreitas, please stop trying to somehow propagate the EFAULT and recover from it. Something is causing bad pointers and/or memory corruption, once that happens any predictable behavior is off the table. I will only accept a patch for this if it turns out the bad pointers are caused by a li

Re: [Libusbx-devel] Announcing libusb-1.0.18-rc1

2014/1/9 Nothing : > > I can not find the conifigure file Maybe that is because the real file name is configure and not conifigure? The archive libusb-1.0.18-rc1.tar.bz2 _DO_ contain the configure file. Of course the github repository do not contain the configure file. But you should use the rel