From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] MTD:NAND: ADD new ECC mode NAND_ECC_HW_OOB_FIRST
Date: Wed, 12 Aug 2009 11:11:28 -0500 [thread overview]
Message-ID: <4A82E9B0.3040306@freescale.com> (raw)
In-Reply-To: <0554BEF07D437848AF01B9C9B5F0BC5D7C6284E6@dlee01.ent.ti.com>
Paulraj, Sandeep wrote:
> [Sandeep] I agree.At the beginning of the year we had a way to do it
> with the existing modes. WE had are own read and write funtions in
> the Davinci NAND driver to achieve what were are doing in this patch.
> But the solution was not accepted by the MTD community. I have given
> the link for the original kernel patches. This current solution had
> the blessings of Thomas Gleixner and David Brownell.
OK. We'll do the same for now, then, but at some point (the
ever-elusive "when I get time") I'd like to try to straighten out the
interface, and shrink the footprint.
-Scott
next prev parent reply other threads:[~2009-08-12 16:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-11 22:34 [U-Boot] [PATCH 2/2] MTD:NAND: ADD new ECC mode NAND_ECC_HW_OOB_FIRST Scott Wood
2009-08-12 11:48 ` Paulraj, Sandeep
2009-08-12 16:11 ` Scott Wood [this message]
[not found] ` <0554BEF07D437848AF01B9C9B5F0BC5D7C628A5C@dlee01.ent.ti.com>
2009-08-12 17:11 ` Scott Wood
2009-08-14 14:03 ` Paulraj, Sandeep
[not found] <7081825318460577925@unknownmsgid>
2009-09-01 15:22 ` John Rigby
2009-09-01 15:36 ` Scott Wood
2009-09-01 16:03 ` Paulraj, Sandeep
2009-09-01 16:31 ` John Rigby
[not found] ` <0554BEF07D437848AF01B9C9B5F0BC5D9217B3B7@dlee01.ent.ti.com>
2009-09-01 16:55 ` John Rigby
2009-09-01 19:19 ` Scott Wood
2009-09-01 19:59 ` Matt Waddel
2009-09-01 20:06 ` Scott Wood
-- strict thread matches above, loose matches on Subject: below --
2009-08-18 16:00 Scott Wood
2009-08-11 22:17 Scott Wood
2009-08-10 17:27 s-paulraj at dal.design.ti.com
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=4A82E9B0.3040306@freescale.com \
--to=scottwood@freescale.com \
--cc=u-boot@lists.denx.de \
/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.