From: David Brownell <david-b@pacbell.net>
To: vimal.newwork@gmail.com
Cc: Linux MTD <linux-mtd@lists.infradead.org>
Subject: Re: query: nand read/write method for 2048 + 64 byte page
Date: Thu, 25 Jun 2009 21:28:08 -0700 [thread overview]
Message-ID: <200906252128.08460.david-b@pacbell.net> (raw)
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.
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
next reply other threads:[~2009-06-26 4:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-26 4:28 David Brownell [this message]
2009-06-26 5:17 ` query: nand read/write method for 2048 + 64 byte page vimal singh
2009-06-26 5:56 ` David Brownell
2009-06-26 11:22 ` vimal singh
2009-06-26 17:10 ` David Brownell
2009-06-27 5:17 ` Amit Kumar Sharma
2009-06-28 6:23 ` vimal singh
-- strict thread matches above, loose matches on Subject: below --
2009-06-23 11:47 vimal singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200906252128.08460.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-mtd@lists.infradead.org \
--cc=vimal.newwork@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox