Re: [Libusbx-devel] xusb: Reading Extended Properties OS Feature Descriptor

2013-07-03 Thread Xiaofan Chen
On Wed, Jul 3, 2013 at 8:17 PM, Julien D'ascenzio wrote: > Ok thanks it's seems to be a windows strangeness : > 'for Interface requests, the WinUSB DLL forces the low byte of wIndex > to the interface number' -> Is that I have observed I believe this is the case. You can try out libusbK drive

Re: [Libusbx-devel] [PATCH] Doc: update hotplug and topology documentation

2013-07-03 Thread Xiaofan Chen
On Thu, Jul 4, 2013 at 5:44 AM, Pete Batard wrote: > If I don't do it today, it'll never happen, so here goes for review. > Looks good to me. Thanks. -- Xiaofan -- This SF.net email is sponsored by Windows: Build for

[Libusbx-devel] [PATCH] Doc: update hotplug and topology documentation

2013-07-03 Thread Pete Batard
If I don't do it today, it'll never happen, so here goes for review. Regards, /Pete >From ba07137acc2123178fed38625c676bb0a478e065 Mon Sep 17 00:00:00 2001 From: Pete Batard Date: Wed, 3 Jul 2013 22:41:55 +0100 Subject: [PATCH] Doc: update hotplug and topology documentation * Also fix some typ

Re: [Libusbx-devel] Unblocking libusb_handle_events()...?

2013-07-03 Thread Orin Eman
I'm pretty sure I use some form of handle events with timeout in the thread that I use to handle events. Each time the thread wakes up, it checks a run flag and if the flag is reset, the thread exits. When it wants the event handler thread to quit, the main code resets the run flag and waits for

[Libusbx-devel] Unblocking libusb_handle_events()...?

2013-07-03 Thread Chris McClelland
Hi libusbx-devel, I'd like to write an application which uses the "simple" async approach. I can't use the polled approach because I'd like my code to be portable to Windows. Here's a scenario: The main thread creates the worker thread, which calls one of the libusb_handle_events_*() varients in

Re: [Libusbx-devel] xusb: Reading Extended Properties OS Feature Descriptor

2013-07-03 Thread Julien D'ascenzio
Ok thanks it's seems to be a windows strangeness : 'for Interface requests, the WinUSB DLL forces the low byte of wIndex to the interface number' -> Is that I have observed -Message d'origine- De : Xiaofan Chen [mailto:xiaof...@gmail.com] Envoyé : mercredi 3 juillet 2013 11:39 À : l

Re: [Libusbx-devel] xusb: Reading Extended Properties OS Feature Descriptor

2013-07-03 Thread Xiaofan Chen
On Wed, Jul 3, 2013 at 5:02 PM, Julien D'ascenzio wrote: > > When I use xusb with my product I have this message: > > Reading Extended Compat ID OS Feature Descriptor (wIndex = 0x0004): > > 28 00 00 00 00 01 04 00 01 00 00 00 00 00 00 00 > (... > > 0010 00 01 57 49 4

[Libusbx-devel] xusb: Reading Extended Properties OS Feature Descriptor

2013-07-03 Thread Julien D'ascenzio
Hi, When I use xusb with my product I have this message: Reading Extended Compat ID OS Feature Descriptor (wIndex = 0x0004): 28 00 00 00 00 01 04 00 01 00 00 00 00 00 00 00 (... 0010 00 01 57 49 4e 55 53 42 00 00 00 00 00 00 00 00 ..WINUSB 0020 00 0