Re: [PATCH 2/2] ubiformat: Leave space for fastmap anchor

[Sascha Hauer <s.hauer@pengutronix.de>]

On Wed, Oct 22, 2014 at 10:15:01AM +0200, Richard Weinberger wrote:
> Am 22.10.2014 um 09:48 schrieb Sascha Hauer:
> > The fastmap code needs a free eraseblock in the first 64 erasblocks
> > to write a fastmap anchor. Since ubiformat continuously writes the
> > image to the flash the fastmap code won't find a free block and
> > fastmap will be disabled. 
> 
> If UBI is unable to write a fastmap it will try again later.
> So, it will be not disabled.
> 
> > With this patch ubiformat skips flashing
> > a block at the beginning thus allowing the fastmap code to write
> > an anchor.
> 
> Hmm, this is a bit hacky. What prevents UBI itself from using this free PEB
> after the first attach? I.e. if a bitflip happens?
> The in kernel code has already a mechanism to move used PEBs < 64 to make space
> for the anchor.

Ah, indeed. I wasn't aware of this. I think we were confused by not
having fm_autoconvert enabled in the kernel and using ubiformat and UBI
from barebox.
So right now I tested that the kernel makes space for the anchor and
has fastmap support on the second attach of an mtd device.

So it seems my problem is solved without patching ubiformat. Nice ;)

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |