On 06/09/2016 06:20 PM, Lars-Peter Clausen wrote: > On 06/09/2016 05:27 PM, Neil Armstrong wrote: >> Hi Sigrok community, >> >> This is a follow-up from the first draft of a Generic IIO driver for Sigrok >> posted at [1]. >> >> Since, I made a backport for the 0.3.0 release and PPA packages to run it on >> current Ubuntu distributions. >> >> The 0.4.0 version is on-going but our ultimate goal is to have it upstreamed >> part of the official sigrok release. >> >> The sigrok IIO development is part of the next BayLibre ACME support via the >> IIO infrastructure, to be able to gather measurements from the Host instead >> of the on-device sigrok instance. >> >> The new repository is https://github.com/baylibre-acme/libsigrok >> >> IIO development branches are : >> - libsigrok-0.3.x-iio for the 0.3.x branch >> - libsigrok-0.4.x-iio for the 0.4.x branch >> >> Before rebasing on master, I would like to have a review of the current >> implementation. >> >> The implementation differs from the previous draft by using channel_group >> instances for each IIO device of a context. >> This gives ability to get multiple probes at the same time, but also be able >> to get a single one by disabling the unwanted groups. > > In my opinion this should rather be addressed by allowing to capture from > multiple device at the same time in e.g. pulseview, rather than grouping > multiple device into a single device and exposing each device as a channel > group.
It's also my opinion, but we actually need this feature for 0.3.x and 0.4.x. Is there a work ongoing to actually provide this in pulseview ? I was wondering if it would be a good idea to expose to sigrok multiple drivers instances, one for all devices and one for each iio devices. This would give a lovely way to select the device under pulseview. > - Lars > Neil ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports. https://ad.doubleclick.net/ddm/clk/305295220;132659582;e _______________________________________________ sigrok-devel mailing list sigrok-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sigrok-devel
