I understand the sentiment of throwing them in a startup script, but I feel like that is giving away some control about the pin use. Although it can temporarly serve as a solution until we are able to fix the configuration in the overlays. Furthermore, I havent found any good documentation about that command(set) (config-pin) so far. And as far as I know pin muxing and configuration is usually set trough device tree overlays.
I'm not rebuilding the device tree blobs. I'm using the dtc command to build device tree overlays, and using the capemanager to load them at runtime. Regards Thomas Op dinsdag 25 april 2017 23:35:24 UTC+2 schreef Greg: > > If the config-pin works, why not put the command(s) in a start-up file and > be done with it? > > Just my opinion, don't touch the device tree blobs unless you absolutely > have to. > And if you have to, use Robert's scripts to rebuild them. > > Regards, > Greg > -- 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/e5b903db-59e2-4e8d-85c3-7ef037881cc0%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
