[PATCH] Newly erased page read workaround

Artem Bityutskiy Artem.Bityutskiy at nokia.com
Fri Apr 1 09:04:41 EDT 2011


On Fri, 2011-04-01 at 14:14 +0200, Ivan Djelic wrote:
> Did you consider this idea: if you have an unused byte available in oob,
> program it to 0x00 when a page is programmed.

I guess this depends on the the controller, but probably this could mean
a substantial write  overhead, not?

> That way, you just need to check a single byte when you read a page in order
> to distinguish erased pages from programmed pages. And by counting the number
> of 1s in the byte, you can be robust to bitflips.

Could you please explain some more what do you mean? So you write the
0x00 byte. Then when you read, you count the number of "1" bits in the
byte. And what exactly this count gives you and to which bitflips you
become robust?

> As a special refinement, you could also "cleanup" pages detected as erased, in
> order to iron out possible bitflips.

What do you mean by "cleanup" a page?

Thanks!

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)




More information about the linux-mtd mailing list