Re: [Libusbx-devel] LitteWire libusb library help

2013-08-06 Thread Tim Roberts
On Aug 6, 2013, at 6:02 PM, Vaclav mailto:vaclav_...@yahoo.com>> wrote: The basic misunderstanding is that I really do not know how does the XP libusb0.dll gets into play. I can have the resulting static library execute the usb_init(), but all I can do is to load the libsub0.dll. Are you famil

Re: [Libusbx-devel] LitteWire libusb library help

2013-08-06 Thread Vaclav
Tim, after reading your note I went back to the ORIGINAL and rather misleading information. The whole problem was that the device driver I did recently installed was for Windows 32 and not for this specific device, as you correctly noted. I actually tested my software I have build few months ag

Re: [Libusbx-devel] LitteWire libusb library help

2013-08-06 Thread Vaclav
Tim, I really appreciate you taking time to respond. I am basically running into a wall when discussing the issue, for many reasons. I will probably use wrong terminology here, please be patient. The device – LittleWire USB “dongle” is basically an interface to hardware and the “inventor “ provi

Re: [Libusbx-devel] RFC: Add libusb_get_vendor_n_product_string function

2013-08-06 Thread Pete Batard
On 2013.08.06 14:57, Alan Stern wrote: > I agree, it does need to change. This means putting more pressure on > manufacturers, not on the users. And how else are you going to put pressure on manufacturers? If Linus and other kernel developers haven't been able to get nVidia to play fair, I'm cu

Re: [Libusbx-devel] [PATCH] Core: Fix potential segfault caused by using freed memory

2013-08-06 Thread Nathan Hjelm
Good catch. I will push this later today. -Nathan On Aug 6, 2013, at 2:16 PM, Chris Dickens wrote: > When a transfer is submitted, the device is referenced in > libusb_submit_transfer() > and unreferenced in usbi_handle_transfer_completion(). This transfer could > potentially > be freed by a

[Libusbx-devel] [PATCH] Core: Fix potential segfault caused by using freed memory

2013-08-06 Thread Chris Dickens
When a transfer is submitted, the device is referenced in libusb_submit_transfer() and unreferenced in usbi_handle_transfer_completion(). This transfer could potentially be freed by any user callback, or is freed by libusb if LIBUSB_TRANSFER_FREE_TRANSFER is set in the flags. The call to unrefer

Re: [Libusbx-devel] LitteWire libusb library help

2013-08-06 Thread Tim Roberts
Vaclav wrote: > > I would like to have a private contact with someone who could give me > some pointers about BASIC libusb build and usage in Windows MFC. MFC is not relevant. That's just a framework for building GUI applications. Did you mean Visual C++? > I have been told by "expert" to use

Re: [Libusbx-devel] RFC: Add libusb_get_vendor_n_product_string function

2013-08-06 Thread Alan Stern
On Tue, 6 Aug 2013, Pete Batard wrote: > > The people we deal with are users, not manufacturers. As a general > > rule, the manufacturers don't listen to us. > > Yeah. And THAT needs to change. > > Everybody is sick and tired of getting subpar FLOSS support from > manufacturers, and that inclu