On Tue, Jul 19, 2016 at 12:24 PM, William Hermans <[email protected]> wrote:
> Ah those! most of them come from loading the cape overlay... >> (cape_universal=enable) >> >> Regards, > > Seriously ? Wow I had no idea. Is this a requirement, or can it be changed > ? Or . . .hmmm how could one modify this behavior so that only what's > needed is loaded. Other than my hackish fix. Or, do we need > cape_universal=enable to use universal-io ? I honestly have not > experimented with disabling cape_universal and temptation to use universal > IO. > So the cape_universal=enable, is just to hook to more easily disable/enable universal-io at bootup. But yeah, what universal-io does, "everything" inside the chip get's enabled, except for the pinmux-ing.. Which you control (the pinmuxing) in userspace.. It's more reliable then loading/unloading individual peripherals, but it has a different cost (memory and possiblly power) Regards, -- Robert Nelson https://rcn-ee.com/ -- 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/CAOCHtYiKAcfVyuK03GSZ_KUZVpTtY1Wv_2WMhuyxAFHRKYKjoQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
