[PATCH 0/2] Support skipping bad blocks when seeking to start address

[goliath]

Hi,

not being between two releases this time, I had some more time to
think about your patch and had a brief discussion with Richard and
subsequently with Boris on the MTD IRC channel.

Some concerns have been raised regarding how your specific boot
loader clutch works and whether we should really add tool support
for it.

If your boot loader seeks to a specific erase block by counting
only good blocks (to load the kernel or some second stage?), what
happens if another block in between goes bad? Does that just brick
your board or do you have to move the data around all the time to
account for that?

What kind of boot loader is this? Is it widely used or is that
algorithm used by a number of other boot loaders? In that case
it would make sense to add support for this. However, if it is
just a one-time fix for a vendor specific boot loader, it might
not be reasonable to merge it into upstream mtd-utils. Or is
there some other use case for this?


Regards,

David