query: nand read/write method for 2048 + 64 byte page

vimal singh vimal.newwork at gmail.com
Fri Jun 26 01:17:31 EDT 2009

On Fri, Jun 26, 2009 at 9:58 AM, David Brownell<david-b at pacbell.net> wrote:
> I noticed
>  http://lists.infradead.org/pipermail/linux-mtd/2009-June/026133.html
> I don't think I understand the question.  But I have two comments
> that might help:
>  - First, the ECC schemes don't dictate much about how the
>   OOB area gets laid out, so what's the problem?  Just pick a
>   layout that doesn't clobber manufacturer bad block markers
>   and you'll be pretty much OK.  Stick all ECC at the end, to
>   keep it simple.
>  - Second, I believe that you will see some issues if you
>   try to have ECC cover the OOB too.  Problem being that
>   the raw_write primitives are used to write OOB data and
>   they don't believe it will be ECC protected.

My point is to protect OOB too (other than ECC bytes).
So, should we implement new OOB area read/write primitives to support this?

And in that case how will we be handling those cases where spare bytes
are protected by clubbing them with main area bytes to generate ECC?
(as example in my previous mail)

> ECC_HW should probably work fine.  You'll just provide your
> own ecclayout struct, and set things up so the NAND core knows
> the hardware works in 512 byte chunks that give 7 byte each of
> ECC data.
> - Dave

\/ | |\/| /-\ |_

More information about the linux-mtd mailing list