android_bootable_recovery/mtdutils
Doug Zongker 22d79a5c5e make offsets in firmware update header not point to bad blocks
(This is being cherry-picked from master.)

hboot will apparently fail to install if the first block of the image
(the one pointed to by the offset in the block 0 header) is a bad
block.  (Hopefully it handles subsequent bad blocks.)

This change makes the MTD write code keep track of the bad blocks it
has skipped over, so that the offset in the header can be adjusted to
be the address of the first successfully written block.

http://b/2358012 - passion: failure to flash hboot (bad blocks?)
2010-01-13 10:07:28 -08:00
..
Android.mk only build flash_image for eng 2009-07-23 15:17:00 -07:00
flash_image.c auto import from //depot/cupcake/@135843 2009-03-03 19:28:42 -08:00
mounts.c auto import from //depot/cupcake/@135843 2009-03-03 19:28:42 -08:00
mounts.h auto import from //depot/cupcake/@135843 2009-03-03 19:28:42 -08:00
mtdutils.c make offsets in firmware update header not point to bad blocks 2010-01-13 10:07:28 -08:00
mtdutils.h make offsets in firmware update header not point to bad blocks 2010-01-13 10:07:28 -08:00