Hi Roman, > Does handling a scope need for so many workarounds? I thought that > this > would be quite easy assuming one uses a library like sigrok?
My point was that the workarounds may be integrated into e.g. openhantek on an application level that's outside the driver. Such workarounds would only work because the device used is known and the inner workings of the driver is known, too. When turning the program into a sigrok client, such workarounds would no longer be supported (as they must be contained in the libsigrok driver), making the adaption a little more difficult. > Sure, and I fear I also won't have the time to do that in the near > future. Still it seemed like a reasonable idea to me as there is > some > quite usable osci interfaces but they mainly lack hardware support > and > sigrok supports quite a broad range of hardware. Reasonable for sure, just... developers, developers, developers ;) All the best, -Soeren ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ sigrok-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sigrok-devel
