On Wed, Jun 24, 2020 at 5:25 PM Rasmus Villemoes rasmus.villemoes@prevas.dk wrote:
On 24/06/2020 04.50, selvamuthukumar v wrote:
On Tue, Jun 23, 2020 at 11:47 PM Tom Rini trini@konsulko.com wrote:
For getting FIT image contents, the existing dumpimage tool handles this.
dumpimage extracts image contents into new files. Current firmware upgrade process in our product is:
- FIT image has kernel and rootfs. Get new FIT image in tmpfs.
- dumpimage to extract the FIT image in tmpfs.
- Write kernel and rootfs in partitions.
many times step2 fails because there is not enough space in tmpfs. FIT image and individual components need to be present in tmpfs. When we mount the FIT image, it does not take extra space tmpfs.
But, why do you use a FIT to bundle the kernel and rootfs? Wouldn't a squashfs image be a better container format? Depending on your rootfs image type, that might even cost even less in tmpfs (and transfer to target) than a FIT.
Platform is based on OpenWRT which already has the FIT image support. Other than kernel and rootfs FIT image has some more contents, like script to upgrade the image from u-boot
I don't have anything against your patch, except as Tom pointed out it really needs to be opt-in so not everybody needs to have libfuse present to build the host tools. Just curious why you've chosen FIT as the container format.
I can make this tool as a configurable option.