From: Gerlando Falauto <gerlando.falauto@keymile.com>
To: Christopher Harvey <charvey@matrox.com>
Cc: "Bigler, Stefan" <Stefan.Bigler@keymile.com>,
Ivan Djelic <ivan.djelic@parrot.com>,
"Brunck, Holger" <Holger.Brunck@keymile.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: state of support for "external ECC hardware"
Date: Thu, 08 Nov 2012 17:37:17 +0100 [thread overview]
Message-ID: <509BDFBD.3030604@keymile.com> (raw)
In-Reply-To: <509BDE9B.3080909@keymile.com>
Hi Chris,
On 11/08/2012 05:32 PM, Gerlando Falauto wrote:
>
>> Ran a trace on some manually inserted bitflips, and the block was moved.
>
> Could you give some pointers on how to manually insert bitflips?
> nanddump/nandwrite from mtd-utils perhaps?
And BTW, wouldn't you also need to explicitly disable on-die ECC in
order to force that, anyway?
Thanks again!
Gerlando
next prev parent reply other threads:[~2012-11-08 16:41 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-29 20:42 state of support for "external ECC hardware" Christopher Harvey
2012-11-08 11:02 ` Gerlando Falauto
2012-11-08 15:21 ` Christopher Harvey
2012-11-08 16:32 ` Gerlando Falauto
2012-11-08 16:37 ` Gerlando Falauto [this message]
2012-11-08 17:03 ` Christopher Harvey
2012-11-08 17:02 ` Christopher Harvey
2012-11-08 19:07 ` Ivan Djelic
2012-11-09 8:46 ` Ricard Wanderlof
2012-11-12 17:19 ` Gerlando Falauto
2012-11-12 17:35 ` Ivan Djelic
2012-11-12 17:39 ` Gerlando Falauto
2012-11-12 18:52 ` Ivan Djelic
2012-11-14 10:12 ` Gerlando Falauto
2012-11-14 13:24 ` Angus CLARK
2012-11-14 14:48 ` Matthieu CASTET
2012-11-14 20:22 ` Ivan Djelic
2012-11-20 11:13 ` Calvin Johnson
2012-11-20 11:35 ` Gerlando Falauto
2012-11-20 12:12 ` Calvin Johnson
2012-11-20 16:16 ` Ricard Wanderlof
2012-11-08 18:59 ` Ivan Djelic
2012-11-08 19:22 ` Christopher Harvey
2012-11-08 19:33 ` Ivan Djelic
2012-11-08 18:04 ` Ivan Djelic
2012-11-14 10:59 ` Angus CLARK
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=509BDFBD.3030604@keymile.com \
--to=gerlando.falauto@keymile.com \
--cc=Holger.Brunck@keymile.com \
--cc=Stefan.Bigler@keymile.com \
--cc=charvey@matrox.com \
--cc=ivan.djelic@parrot.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 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.