From: David Brownell <david-b@pacbell.net>
To: davinci-linux-open-source@linux.davincidsp.com,
Troy Kisky <troy.kisky@boundarydevices.com>,
"Paulraj, Sandeep" <s-paulraj@ti.com>
Cc: "dwmw2@infradead.org" <dwmw2@infradead.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>
Subject: Re: [PATCH v2 3/3] Add 4-bit ECC support for large page NAND chips on Davinci
Date: Thu, 18 Jun 2009 19:07:00 -0700 [thread overview]
Message-ID: <200906181907.00408.david-b@pacbell.net> (raw)
In-Reply-To: <4A3AB748.8080901@boundarydevices.com>
On Thursday 18 June 2009, Troy Kisky wrote:
> > To answer your question, yes it can be at the end but I do not
> > see any reason why it has to be at the end
> > Any reason why you insist that it should be at the end.
>
> Well, for one, it is nice to have oobfree contiguous. But mainly, I hope
> to eventually use a default layout which will have the oob data at the
> end when 0 holds the badblock marker.
Also, I thought the agreement from previous discussions was to
put it at the end, keeping a contiguous oobfree area ... which
is why the OpenOCD [1] DaVinci NAND driver puts it at the end in
the standard HWECC4 mode (not HWECC4_INFIX):
- with 2K pages ... ECC in bytes 24..63 inclusive.
- with 4K pages ... ECC in bytes 48..127 inclusive.
Now, the 0.2.0 release for that hasn't frozen yet, but the idea
was to have it match what Linux does.
So if the plans for Linux change, make sure I know so I can submit
a patch ... though I'd rather see the previous agreement kept.
- Dave
[1] http://openocd.berlios.de/doc/html/index.html
prev parent reply other threads:[~2009-06-19 2:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 20:23 [PATCH v2 3/3] Add 4-bit ECC support for large page NAND chips on Davinci s-paulraj
2009-06-18 21:16 ` Troy Kisky
2009-06-18 21:34 ` Paulraj, Sandeep
2009-06-18 21:53 ` Troy Kisky
2009-06-19 2:07 ` David Brownell [this message]
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=200906181907.00408.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=akpm@linux-foundation.org \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=s-paulraj@ti.com \
--cc=tglx@linutronix.de \
--cc=troy.kisky@boundarydevices.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.