![]() ![]() ![]() OK, I created something to update my kernel and devicetree. ![]() I don’t think there is a way to shrink a UBIFS or a UBI volume, hence the only way doing this is using U-Boot and deleting the volume entirely… (which is what our update scripts do, see prepare_ubi in flash_blk.scr, introduced with this change). The problem remaining however is that switching to that new format requires to create new UBI volumes… In V2.5 all space has been consumed by the rootfs, hence it also requires a resizing of the root file system. A postinst script for the kernel package could call those scripts and hence update the kernel/device tree on the volumes. However, even though the separate UBI volumes are not directly accessible, there is ubiupdatevol which allows to write UBI volumes from Linux. It also works well for boot scenarios with initramfs. It was also an advice of UBI co-author Richard Weinberger. The reason we switched to the new boot mode with independent UBI volumes is to lower the risk that the boot loader corrupts the root file system. Using the package manager to update the kernel might have worked so far, but it is not an update mode we explicitly test and maintain… Our default, tested update mode is through the update scripts in U-Boot. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |