err, I kind of messed that post up. but the question is still valid, just hanging off the wrong post. But I was curious what you mentioned in your last post.
> adding "of_overlay_disable" to the boot arg's kills it. So I find this a little confusing. This means we're able to disable the kernel / userspace cap manager, or the uboot cape manager? The later doesn't make sense to me. what who says that it needs to ? On Thu, Dec 29, 2016 at 5:36 PM, William Hermans <[email protected]> wrote: > > > On Thu, Dec 29, 2016 at 3:16 PM, Robert Nelson <[email protected]> > wrote: > >> > First issue... Now the Kernel Cape Manager get's in the way, i need to >> > pass a global kill switch (or find the global disable), right now you >> > have to "disable" capes loaded by U-Boot.. (you don't have too, it >> > just looks weird when they both load fine..) >> >> adding "of_overlay_disable" to the boot arg's kills it.. >> > > Additionally to the previous post I've made. So assuming I leave my > dtb=<board file I want loaded> in to bypass the default behavior. Does this > work in this manner ? e.g. I need a specific, and custom board file to load > at boot. > -- 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/CALHSORq%2BNnkaV2ndNB5-5D%3DT7xHfY%2Bq_DmvpHPf9vNkaN71oCA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
