Re: choosing a file system to use on NAND/UBI

[Artem Bityutskiy <dedekind@infradead.org>]

On Mon, 2008-04-07 at 22:22 +1000, Hamish Moffatt wrote:
> My idea is that you can "ubiupdatevol /dev/ubi0_0 myimage.gz", which
> ubiupdatevol would decompress on the fly. You could decompress it
> somewhere first but it may not fit in RAM (and writing it to flash
> temporarily would be slower).

So you want some kind of "live" updates? You have your device which is
running. And you want to update one of your UBI volumes. You copy the
update image to the device and want to use ubiupdatevol to put it to the
volume.

How do you copy the file? If you have network connection, may be you
could teach ubifs to take the image from the network? dwmw2 also
recently added an utility to mtd-utils.git which _seems_ to be doing
this, so you could teach it to update the volume which should be very
easy (see recv_image and serve_image in mtd-utils.git).

> Looking at the code I see the main issue is that you need to know the
> file size before you start updating.
Yeah, that is right. This is what UBI update ictl expects. But probably
gzip has this info somewhere in its meta-data.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)