1) While I'm always grateful for your responses, TJF, you need to understand that your answers almost always come across a bit ... abrupt. I presume it's a language thing as I couldn't possibly convey nuance in German.
2) You know the libpruio architecture cold, but none of your documentation explains it, at all. So, the relationship between kernel module, system groups, PRU, and user mode is not at all clear to newcomers who actually try to look at your libpruio library. 3) The reliance on FreeBASIC is an absolute non-starter for a *LOT* of people. While I'm sure you find it to be a superior tool, most people already find the BeagleBone forbidding enough. Adding another unfamiliar tool to the mix is not something most people are willing to do. Thanks. On Sunday, June 21, 2020 at 11:22:48 PM UTC-7, TJF wrote: > > > > Am Montag, 22. Juni 2020 07:45:44 UTC+2 schrieb Andrew P. Lentvorski: >> >> Neither userspace nor PRU can change a pinmux. >> > > Not correct. In a libpruio configuration all members of system-group > 'pruio' can pinmux from user space. That's why libpruio development is as > easy as Arduino development, but much more powerful. > *Because* you shunt the request through the custom kernel module. Telling people that they can pinmux from userspace simply confuses people further who are already probably plenty confused. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/9e313800-286e-41fa-b20f-cee927ab9d1co%40googlegroups.com.
