On Fri, Apr 26, 2019 at 04:42:35PM +0200, Enrico Weigelt, metux IT consult wrote: > On 26.04.19 15:36, Jan Kiszka wrote: > > > At the same time, there are no real alternatives - to my> knowledge - for the value it brings (various bindings) to simply > switch> the engine. > Which value exactly does that collection of crude wrappers and broken > attempts to buypass the kernel (driving gpios via /dev/mem *facepalm*) > provide ? > /dev/mem access to gpio's were done during the sysfs days (yes to bypass the kernel interface) but now mraa will use chardev if the kernel is chardev supported. Still, it just behaves the way you want (/dev/mem was also optional back then) and I couldn't find a better alternative for playing in the userspace with multiple languages. -Mani > mraa belongs to the category of software, I would never put onto any > production system. (yes, I already had a client who asked me to repair > his mraa-based software. finally, I've replaced mraa w/ a few LoC ...) > > > --mtx > > -- > Enrico Weigelt, metux IT consult > Free software and Linux embedded engineering > info@xxxxxxxxx -- +49-151-27565287