On Wed, Mar 5, 2014 at 10:19 AM, porkupan <[email protected]> wrote: > Yeah, I was thinking about something like this. But since I am making a > video controller overlay, it is better if it had been loaded at kernel > initialization, and not as part of the init scripts. I'd like the display > to be available to show some kernel startup. So I will either just > overwrite the cape-bone-dvi-00A0.dts with my own stuff (and make a custom > Sunhillo-only patch), or will add a new overlay to KERNEL/firmware/Makefile. > > It seems that a lot of people got confused by this issue (long discussion > here). The problem is, the available documentation for 3.8 kernel seems to > imply that the /lib/firmware overlay files are available for startup load, > so it would be helpful if qualification was added.
If you disable "CONFIG_FIRMWARE_IN_KERNEL" in the kernel build it should search /lib/firmware/*.dtbo Last i tried it caused a significant bootup delay, so i oped to just build them all in by default.. Regards, -- Robert Nelson http://www.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]. For more options, visit https://groups.google.com/groups/opt_out.
