Hi! There is some basic documentation on the wiki:
https://sigrok.org/wiki/Hardware_driver_API I personally don't find the API that bad, though I would prefer if this could be C++, that is a matter of choice. The API seems pretty straightforward, however I have never implemented a device, so I can't tell if there are hidden issues underneath (I expect there are some nasty hacks/workarounds when people tried to implement something "smart"). It'd be nice if we could get a pointer to the issues Soeren has with the API (I don't know where that quote came from and don't want to look through all of this messages, googling the quote gets me this thread... I'd be to happy to read the relevant conversation if you can link it). Perhaps this can be improved somehow, or we can at least be aware of the problems. (many of API issues can be fixed by a little bit of documentation and a discipline -- not saying this is or is not the case). Cheers, Ladislav On Wed, Oct 15, 2025 at 09:08:19AM +0200, Steve Schnepp wrote: > On Mon, Oct 13, 2025 at 11:44 AM Soeren Apel <[email protected]> wrote: > > The two core issues for me are that libsigrok's architecture is > > fundamentally outdated and that it is *impossible* for me to review and > > merge changes to libsigrok device drivers. > > Is there a documented API for device drivers to implement ? > > -- > Steve Schnepp -- S pozdravem Ladislav "Krakonoš" Láska http://www.krakonos.org/ _______________________________________________ sigrok-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/sigrok-devel
