OK, I did not understand that about Universal IO overlays! Another question: I see the univ-emmc cape gets loaded after activating Remoteproc kernel modules. This is correct and expected behavior? I was a little surprised to see the coupling between device tree and kernel modules in this manner.
Very big fan here of Universal IO! Device tree hassles a seriously large entry barrier for newbies like myself. Two thumbs up for Universal IO! On Saturday, November 12, 2016 at 11:53:26 AM UTC-5, RobertCNelson wrote: > > On Nov 12, 2016 10:39 AM, "Greg" <[email protected] <javascript:>> > wrote: > > > > Is there a better way to get the job done? Or better "don't touch that"? > > Yeap, the reliably way to unload the cape is to reboot.. this is why the > cape universal with config-pin is so useful.. config-pin allows us to map a > pin as function A then change it to function B without rebooting. > > Regards, > -- 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/367f1605-c96e-4d64-80b3-fe73b8ab62d6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
