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 <https://groups.google.com/d/topic/beagleboard/Iem_mHknIUM/discussion>). 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. On Wednesday, March 5, 2014 11:06:04 AM UTC-5, RobertCNelson wrote: > > On Wed, Mar 5, 2014 at 10:02 AM, porkupan <vladimi...@gmail.com<javascript:>> > wrote: > > I guess, I should have realized that the filesystems get mounted only > after > > the DT overlays are loaded. So only the DT overlays linked directly > into > > the kernel image (as part of the kernel build) are available at startup > > time. Well, this sucks, but at least I know what to do now. > > As a workaround in the debian images ( i need to write something > similar for the ubuntu images) > > I wrote a generic init script that does "echo cape > > /sys/devices/bone_capemgr.9/slots" on startup to bypass this probme... > > > https://github.com/RobertCNelson/omap-image-builder/blob/master/target/init_scripts/capemgr-debian.sh > > > 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 beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
