[RFC] [PATCH 1/1] [MTD] UBI: implement per-volume update

Frank Haverkamp haver at vnet.ibm.com
Thu Feb 1 08:35:45 EST 2007


Hi Thomas,

On Thu, 2007-02-01 at 14:10 +0100, Thomas Gleixner wrote:
> On Thu, 2007-02-01 at 12:21 +0200, Artem Bityutskiy wrote:
> > This patch removes the global update marker support and everything
> > related to it. Now we have per-volume update marker bit in the
> > volume table. This makes us incompatible with older UBI images but
> > this is not a big deal - UBI is not used so widely so far and we
> > can afford dropping legacy stuff now.
> 
> Uuurgh. Incompatible in what way ? Does this mean you cannot boot from
> an existing image anymore ?

No if that would be the case, I would have objected to the patch.
What it should do is to remove the need to have the update marker
block. Instead of the update marker block Alexander is using a flag in
the volume info table per volume to indicate that an update is going on.

> 
> 	tglx

The compatibility issue is that if you want to update a system with 
a not yet cleaned up "old style update marker" the new kernel does
not know what to do with the now unknown ubi-update-volume. The
compatibility flag we decided for the update-volume is "reject", which
will cause ubi not to accept the mtd.

Frank





More information about the linux-mtd mailing list