Hi Mark,

cmpxchg wrote:
> - 24 MHz sampling reliability
> 
> I found that the libusb callbacks are acknowledged with libsigrok
> hardware-specific api.c's libusb_handle_events_timeout(ctx, tv). When I
> changed this to libusb_handle_events_completed(ctx, 0) the sampling became
> more consistent and in line with the libusb documentation recommendation
> (preventing raceconditions)
> 
> The latter is a libusb.org / libusbx.org / libusb.info library usage issue.
> I see the usb completion code is duplicated in a lot of places, perhaps this
> can be done using a libsigrok internal common api.

I have some changes in mind for how libsigrok uses libusb. I don't
expect anyone else to implement them, and it might be a while until I
get to it, but you're absolutely right that there's good potential
for more code reuse within libsigrok. That's where I want to head.


//Peter

------------------------------------------------------------------------------
Flow-based real-time traffic analytics software. Cisco certified tool.
Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer
Customize your own dashboards, set traffic alerts and generate reports.
Network behavioral analysis & security monitoring. All-in-one tool.
http://pubads.g.doubleclick.net/gampad/clk?id=126839071&iu=/4140/ostg.clktrk
_______________________________________________
sigrok-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/sigrok-devel

Reply via email to