On Tue, Mar 04, 2014 at 08:16:52PM +0100, Daniel Elstner wrote:
> 
> as I'm not using Windows I can't test this myself. But I have opened a
> bug to track the problem:
> 
> http://sigrok.org/bugzilla/show_bug.cgi?id=328
> 
> > I also tried set some trigger mode, but unsuccessfull. Where could be
> > the problem?
> 
> It looks like the driver does not even receive the periodic timeout
> callbacks when using the asynchronous API of libusb. No idea why; it
> works fine for me on Linux.

It's likely this is an issue with the Windows USB handling code in
hardware/common/usb.c, which is a quick hack I wrote to overcome the
fact that most USB drivers didn't previously work in Windows at all.

The problem at the time was that since libusb_get_pollfds() doesn't
exist on Windows, there was no way to add USB devices to the set of
things being waited on by the libsigrok session's main g_poll loop.

I hacked around this by spawning a background thread which just runs
libusb_wait_for_event(), then signals a Win32 event handle. That event
handle can then be added to the g_poll set as a substitute for the
normal libusb pollfds.

This got a lot of things working but I'm guessing is still an
incomplete solution.


Martin

------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works. 
Faster operations. Version large binaries.  Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
sigrok-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Reply via email to