Handling badblock in MTD

[David Woodhouse]

On Thu, 2007-08-16 at 15:10 +0530, Raj Kumar Yadav wrote:
> 
> It seems, the block is bad to an extent that the erase also have no effect.
> This means that, I cannot mark the block bad, as the first page is all 0xff
> and write on the page has no effect on page data.
> 
> So, ending up to a situation, where the block will never be marked bad, and
> the write will always fail (due to MTD NAND verify) on the block pages.
> 
> Currently, we are using the first byte of the first page in the Block to
> detect/mark the block as bad.
> 
> What is the standard solution for this, Should the second page also be used
> for detecting the bad block in MTD nand layer. But then how far we can go
> about adding the pages to detect/mark bad block. 
> 
> Is there any better method/policy to deal with it? 

Use a bad block table.

-- 
dwmw2