From: Brian Norris <computersforpeace@gmail.com>
To: Gerhard Sittig <gsi@denx.de>
Cc: David Mosberger <davidm@egauge.net>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Gupta, Pekon" <pekon@ti.com>,
"dedekind1@gmail.com" <dedekind1@gmail.com>
Subject: Re: [PATCH] mtd: nand: Add support for Micron on-die ECC controller (rev2).
Date: Tue, 1 Apr 2014 01:47:18 -0700 [thread overview]
Message-ID: <20140401084718.GH6400@brian-ubuntu> (raw)
In-Reply-To: <20140328125600.GC3998@book.gsilab.sittig.org>
On Fri, Mar 28, 2014 at 01:56:00PM +0100, Gerhard Sittig wrote:
> There must have been a reason for the
> introduction of the "oob_required" condition -- I just understood
> it was other MLC chips, not the on-die-ECC that we are talking
> about here.
'oob_required' is really only there for hardware which optimizes the
no-OOB case for program and read (I have an out-of-tree driver for
hardware whose DMA engine accelerates data-only read/program; ECC is
done on-the-fly in hardware).
Brian
next prev parent reply other threads:[~2014-04-01 8:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 23:05 [PATCH] mtd: nand: Add support for Micron on-die ECC controller (rev2) David Mosberger
2014-03-27 6:56 ` Gupta, Pekon
2014-03-27 11:27 ` Gerhard Sittig
2014-03-27 19:28 ` David Mosberger
2014-03-28 12:56 ` Gerhard Sittig
2014-03-28 15:40 ` David Mosberger
2014-04-01 8:47 ` Brian Norris [this message]
2014-03-28 8:37 ` Gupta, Pekon
2014-03-28 12:43 ` Gerhard Sittig
2014-03-28 17:27 ` Gupta, Pekon
2014-03-28 15:52 ` David Mosberger
2014-04-01 8:36 ` Brian Norris
[not found] ` <CALnQHM3r9DDqjmo=s1aFLgob+ztzfqjVrGbOS9QWGLKB+nv=fQ@mail.gmail.com>
2014-04-01 15:10 ` Fwd: " David Mosberger
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=20140401084718.GH6400@brian-ubuntu \
--to=computersforpeace@gmail.com \
--cc=davidm@egauge.net \
--cc=dedekind1@gmail.com \
--cc=gsi@denx.de \
--cc=linux-mtd@lists.infradead.org \
--cc=pekon@ti.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