[PATCH] [RFC] tools: fitmount: fuse mount fit images

Rasmus Villemoes rasmus.villemoes at prevas.dk
Wed Jun 24 13:55:30 CEST 2020


On 24/06/2020 04.50, selvamuthukumar v wrote:
> On Tue, Jun 23, 2020 at 11:47 PM Tom Rini <trini at 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:
> 
> 1. FIT image has kernel and rootfs. Get new FIT image in tmpfs.
> 2. dumpimage to extract the FIT image in tmpfs.
> 3. 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.

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.

Rasmus


More information about the U-Boot mailing list