Am Samstag, 24. März 2018 02:54:19 UTC+1 schrieb [email protected]: > > Okay awesome, thank you! > > This weekend I will get a chance to dig into this more. So a lot of the > examples I've seen using uio_pruss involve a device tree overlay for gpio > pin muxing, I'm comfortable doing that, but I've noticed lately that slots > isn't around anymore because I guess a lot of people were messing things up > by echoing into it. Should I still be using an overlay to do my pins? Or > would something like config-pin work just fine? >
For development phase, flexibility is important (after boot pinmuxing). Once your design is finished, a matching overlay is advantageous (pinmuxing at boot time, faster, less memory). Use either config-pin or libpruio-00A0.dtbo for punmuxing (the later is more save). The slots file was removed since any 4.x kernel (>4.4 AFAIR). Never kernels are not good documented, and you'll find different examples. It's hard to keep track. From my point of view, they're still experimental. If you want fast and successful development, I recommend falling back to a 3.8 kernel. You'll find good documented examples, and you'll get to a steep learning curve. You can switch to a never kernel later, when you know what you need. -- 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/4915612f-53a1-49e1-bf52-18365a34dc79%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
