On Fri, 8 Nov 2013 22:38:52 +0100, Mathias Grimmberger <[email protected]> wrote:
> But one thing isn't clear to me. The remaining code is about reading > the sample memory when the scope is stopped. How to indicate the > capability in the device options, and how to tell sigrok-cli to use > that mode instead of live capture? The configuration key SR_CONF_DATA_SOURCE does that. It has currently only been used in datalogger devices, but it's pretty generic: http://sigrok.org/gitweb/?p=libsigrok.git;a=blob;f=libsigrok.h;h=17d7fc17d7a5249dff9d11c585ec95891bb596d9;hb=HEAD#l727 The value is a freeform string -- not ideal, but that does make it flexible. It's currently always "Live" or "Memory" now, so you'd tell sigrok-cli about it like this: sigrok-cli ... --config data_source=Memory ... Take a look at the uni-t-ut32x driver for an example. -- Bert Vermeulen [email protected] email/xmpp ------------------------------------------------------------------------------ November Webinars for C, C++, Fortran Developers Accelerate application performance with scalable programming models. Explore techniques for threading, error checking, porting, and tuning. Get the most from the latest Intel processors and coprocessors. See abstracts and register http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk _______________________________________________ sigrok-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sigrok-devel
