[PATCH] mtd: nand: add option to erase NAND blocks even if detected as bad.

Richard Weinberger richard.weinberger at gmail.com
Fri May 12 01:12:30 PDT 2017


Mario,

On Fri, May 12, 2017 at 7:39 AM, Mario J. Rugiero <mrugiero at gmail.com> wrote:
> Some chips used under a custom vendor driver can get their blocks
> incorrectly detected as bad blocks, out of incompatibilities
> between such drivers and MTD drivers.
> When there are too many misdetected bad blocks, the device becomes
> unusable because a bad block table can't be allocated, aside from
> all the legitimately good blocks which become unusable under these
> conditions.
> This adds a build option to workaround the issue by enabling the
> user to free up space regardless of what the driver thinks about
> the blocks.

Hmm, this sounds like a gross hack.

> Example usage: recovering NAND chips on sunxi devices, as explained
> here: http://linux-sunxi.org/Mainline_NAND_Howto#Known_issues

What this wiki suggests is not wise.
How can you know which blocks are really bad and which not?

-- 
Thanks,
//richard



More information about the linux-mtd mailing list