From: Brian Norris <computersforpeace@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: Tim Harvey <tharvey@gateworks.com>,
Artem Bityutskiy <dedekind1@gmail.com>,
Adrian Hunter <adrian.hunter@intel.com>,
linux-mtd@lists.infradead.org,
Elie De Brauwer <eliedebrauwer@gmail.com>,
Huang Shijie <shijie.huang@arm.com>,
Boris Brezillon <boris.brezillon@free-electrons.com>
Subject: Re: UBIFS corruption after power cut - possibly unstable bits issue?
Date: Mon, 2 Nov 2015 14:11:36 -0800 [thread overview]
Message-ID: <20151102221136.GF7274@google.com> (raw)
In-Reply-To: <5637D649.8060802@nod.at>
+ Boris
On Mon, Nov 02, 2015 at 10:31:53PM +0100, Richard Weinberger wrote:
> Am 02.11.2015 um 21:31 schrieb Tim Harvey:
>
> >> I've cc'd Huang, Elie, and Brian who were involved in the patch to
> >> detect bit-flips in gpmi-nand.c reads - perhaps they have some more
> >> ideas. I find it interesting that in one case that patch resolves the
> >> issue and in the other it does not.
>
> Yeah, good idea!
Sorry, I don't have much time to care about gpmi-nand right now. I
recall that there was ugly support for detecting bitflips in erased
pages posted at some point (in case that's relevant; didn't read the
whole essay), but that never got merged, and Huang left Freescale.
I also recall Boris struggled with that driver at some point. Perhaps he
can be persuaded to care.
Brian
next prev parent reply other threads:[~2015-11-02 22:12 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-26 19:37 UBIFS corruption after power cut - possibly unstable bits issue? Tim Harvey
2015-10-26 20:01 ` Richard Weinberger
2015-10-26 20:31 ` Tim Harvey
2015-10-26 21:41 ` Richard Weinberger
2015-10-27 19:01 ` Tim Harvey
2015-10-27 19:52 ` Richard Weinberger
2015-11-02 20:27 ` Tim Harvey
2015-11-02 20:31 ` Tim Harvey
2015-11-02 21:31 ` Richard Weinberger
2015-11-02 22:11 ` Brian Norris [this message]
2015-11-03 13:38 ` Boris Brezillon
2015-11-16 15:01 ` Tim Harvey
2015-11-30 21:58 ` Tim Harvey
2015-12-01 9:12 ` Boris Brezillon
2015-11-03 9:10 ` Artem Bityutskiy
2015-11-03 10:06 ` Michal Suchanek
2015-11-03 10:18 ` Ricard Wanderlof
2015-11-03 10:43 ` Artem Bityutskiy
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=20151102221136.GF7274@google.com \
--to=computersforpeace@gmail.com \
--cc=adrian.hunter@intel.com \
--cc=boris.brezillon@free-electrons.com \
--cc=dedekind1@gmail.com \
--cc=eliedebrauwer@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
--cc=shijie.huang@arm.com \
--cc=tharvey@gateworks.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 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.