On Fri, Dec 23, 2016 at 5:58 PM, Robert Nelson <[email protected]> wrote:
> For those interfaces, there's not a lot of overlay loading issues on > the kernel side. The biggest change, you should see your pin's taken > earlier and more consistently at bootup. You can also optimize your > boot time more, as one of the big reasons everything we have is built > as a module, is just too make the kernel overlays work more reliable. > I wonder if this will help mitigate, at least *some* of the big boot "lag" waiting on network interfaces to come up. That alone, if so, would be a huge plus. Anyway, the steps you've listed above will work on emmc as well as sdcard ? Additionally, although perhaps not related to this per se. I'd really like to see some sort of boot options where "we" did not have to write an environment file for the sdcard *if* we just wanted to boot from the emmc, but would like an sdcard inserted for extra storage. That is, without having to hack the second stage bootloader. Or is that a big deal for you guys ? You know, I'm not even sure how that would work . . .honestly this just popped into my head right now. -- 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/CALHSORqq1CZKjFK_EpBUDdERgqE0Gh3407ckKOxR4GxJMEWc_g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
