Can ID the NAND chip, but every erase block is bad?

[Bill Gatliff]

David Woodhouse wrote:
> Take a closer look at how bad blocks were detected under 2.6.20.
>
> A virgin chip will use a certain byte in the spare area of each
> eraseblock to mark that block as bad. But often we reclaim those bytes
> and transcribe the information into a bad block table elsewhere on the
> flash.
>
> Booting a kernel which ignores the bad block table and looks for the bad
> block markers in the original location will have fairly much the effect
> you describe.
>   

Ok, I'll take a look into that code.

Is there any way to instruct MTD to discard any previous bad block
information, and reconstruct the bad block table from scratch?


b.g.

-- 
Bill Gatliff
Embedded systems training and consulting
http://billgatliff.com
bgat at billgatliff.com