tag 02d24c16d63e1e1c2ed18b72fd68c3695c647dda
tagger The Android Open Source Project <initial-contribution@android.com> Tue Mar 30 15:15:17 2010 -0700
object 22d79a5c5eab9c1e86ff2af210bb072689e2d630

Android 2.1 release 2.1p

commit 22d79a5c5eab9c1e86ff2af210bb072689e2d630
author Doug Zongker <dougz@android.com> Tue Jan 12 16:18:33 2010 -0800
committer Doug Zongker <dougz@android.com> Wed Jan 13 10:07:28 2010 -0800
tree 866d289588e7c19e5218ce5aafbf9430bb274e99
parent 17a47098d2a4214397f8b30e2692c9487d7ab5ff

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?)