Dear Soeren! Thanks for the extensive answer.
Am 2016-10-09 um 20:01 schrieb Soeren Apel: > For those reasons, the most sensible way to go wouldn't be to > merge but instead to fork those projects and replace their > internal drivers by a generic sigrok interface, turning the > software into another sigrok client. This would certainly > be doable, although it may prove difficult to handle all the > workarounds that can be used when interacting with a known > scope directly. Does handling a scope need for so many workarounds? I thought that this would be quite easy assuming one uses a library like sigrok? > So in the end it's a matter of "is it worth it?" and "who > volunteers to do it?" - so far no one has stepped up, so > it hasn't been done :) 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. cheers, roman ------------------------------------------------------------------------------ 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
