From: Thomas Gleixner <tglx@linutronix.de>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org,
David Woodhouse <David.Woodhouse@intel.com>,
Artem Bityutskiy <dedekind1@gmail.com>
Subject: Re: nand_base - kill chip->oob_poi?
Date: Wed, 28 Mar 2012 11:51:42 +0200 (CEST) [thread overview]
Message-ID: <alpine.LFD.2.02.1203281149010.2542@ionos> (raw)
In-Reply-To: <CAN8TOE_8sTtuvBq+SOSLv5Kbw_2G8ByX-euiDm=z2btO-kLkcw@mail.gmail.com>
On Tue, 27 Mar 2012, Brian Norris wrote:
> Hi,
>
> I'm looking to support a new NAND hardware controller, and it doesn't
> support OOB read/write for its fastest modes of operation, since most
> normal activity (i.e., UBI(FS)) doesn't need OOB. So I'm trying to
And how is ECC working for that "normal" activity ?
Using NAND w/o ECC is doomed for fail.
Aside of that improvements to the NAND code are always welcome,
modifications which are solely done to support insane usage of NAND
FLASH not so much.
Thanks,
tglx
next prev parent reply other threads:[~2012-03-28 9:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-28 1:55 nand_base - kill chip->oob_poi? Brian Norris
2012-03-28 9:51 ` Thomas Gleixner [this message]
2012-03-28 10:14 ` Woodhouse, David
2012-03-28 16:42 ` Brian Norris
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=alpine.LFD.2.02.1203281149010.2542@ionos \
--to=tglx@linutronix.de \
--cc=David.Woodhouse@intel.com \
--cc=computersforpeace@gmail.com \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
/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