Hi Jeffy, On Tue, Feb 02, 2016 at 04:43:31PM +0800, Jeffy Chen wrote: > We should count skipped blocks in when calculating write offset. > > Signed-off-by: Jeffy Chen <jeffy.c...@rock-chips.com>
As I told you, this won't work in the NAND case. If there's a bad block in the NAND, the offset will be incremented by a block, and it won't be taken into account by the fastboot client, and you'll end up writing on a block you already wrote to. I guess the only solution is to make the storage backend scan the area you skip so that it adjusts the skipped size, possibly extending it. Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
