From: Gerhard Sittig <gsi@denx.de>
To: Brian Norris <computersforpeace@gmail.com>
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: [RFC] mtd: nand: Preparatory patch for adding on-die ECC controller support. This patch adds NAND_ECC_HW_ON_DIE and all other changes to generic code.
Date: Tue, 1 Apr 2014 15:49:18 +0200 [thread overview]
Message-ID: <20140401134908.GP2775@book.gsilab.sittig.org> (raw)
In-Reply-To: <20140401091237.GI6400@brian-ubuntu>
On Tue, 2014-04-01 at 02:12 -0700, Brian Norris wrote:
>
> BTW, do these flash power on in any particular default mode? Can you
> order versions that have on-die ECC enabeld/disabled by default? Is that
> perhaps what the READ_ID "Internal ECC" flag actually means
> (disabled/enabled by default)?
According to the datasheet the chips come out of RESET with
on-die-ECC disabled. The setup that I have seen does enable the
in-chip feature within an early loader. Subsequently running
bootloaders and OSes (here: U-Boot and Linux) find the chip with
on-die-ECC enabled.
I understand that READ_ID will tell you whether on-die-ECC is
supported by the chip. The GETFEATURE request tells you whether
it's enabled. And SETFEATURE allows you to control whether it's
enabled or disabled.
virtually yours
Gerhard Sittig
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr. 5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office@denx.de
prev parent reply other threads:[~2014-04-01 13:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-28 2:58 [RFC] mtd: nand: Preparatory patch for adding on-die ECC controller support. This patch adds NAND_ECC_HW_ON_DIE and all other changes to generic code David Mosberger
2014-03-28 5:48 ` Gupta, Pekon
2014-03-28 13:05 ` Gerhard Sittig
2014-03-28 16:19 ` David Mosberger
2014-04-01 9:12 ` Brian Norris
2014-04-01 13:49 ` Gerhard Sittig [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=20140401134908.GP2775@book.gsilab.sittig.org \
--to=gsi@denx.de \
--cc=computersforpeace@gmail.com \
--cc=davidm@egauge.net \
--cc=dedekind1@gmail.com \
--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