Hi Zach, So, first of all. Yes removing the line , commenting it out in uEnv.txt will keep from loading the overlay at boot. As for removing it from the initramfs, I would assume if you reversed the process. e.g. remove the line from uEnv.txt. then remove the file from /lib/firmware, that the script would also remove it from the initramfs. However, I have not looked through the script in that great of detail, and have not tested it personally.
The only real issue here is that the initramfs could get much larger than you needed, in some cases. But otherwise it should be fine. So long as you do not create too many overlays, and "inject" them into the initramfs. In dire cases, where you do need to remove much fromm the initramfs, you could copy the initramfs, extract the file system, modify the file system, re-archive it, then move the old initramfs out of the way, and replace it with the new initial ram disk. It is a rather complex operation, and that would be assuming Roberts script is not already capable of removing files as well. On Fri, Nov 11, 2016 at 2:01 PM, Zach B <zbron...@gmail.com> wrote: > Great, thanks! And not to be a pest but I assume in order to undo that > change I simply comment the line that I add to the uEnv.txt and that's it? > Should I worry about removing the *.dtbo object from the initrd? > > On Friday, November 11, 2016 at 3:22:17 PM UTC-5, RobertCNelson wrote: > >> On Fri, Nov 11, 2016 at 2:14 PM, Zach B <zbro...@gmail.com> wrote: >> > Thanks Robert! That solved the problem I have been having. The overlay >> > loaded and everything looks to be working. One follow up question I do >> have >> > is what is the proper way to load a custom overlay on startup? Is there >> a >> > way to enable multiple overlays as long as they don't try to use the >> same >> > pins? >> >> Add it /boot/uEnv.txt: >> >> ##Example v4.1.x >> #cape_disable=bone_capemgr.disable_partno= >> #cape_enable=bone_capemgr.enable_partno= >> >> ##Example v4.1.x >> #cape_disable=bone_capemgr.disable_partno= >> cape_enable=bone_capemgr.enable_partno=PRU-GPIO-BLINK >> >> You'll need to copy PRU-GPIO-BLINK-00A0.dtbo to /lib/firmware/ >> >> then run: >> >> sudo /opt/scripts/tools/developers/update_initrd.sh >> >> To copy the new *.dtbo object into the initrd.. >> >> Then just reboot, and you should see your overlay loaded.. >> >> 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 beagleboard+unsubscr...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/beagleboard/18dbb804-b0c2-495f-bd95-14a933c84022%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/18dbb804-b0c2-495f-bd95-14a933c84022%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORp9AS-PO6d9rkfwoPdWPAM4VF%2BUa14wV7JZoQDKbUXjfA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
