From: shijie8@gmail.com (Huang Shijie)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 0/3] mtd: nand: gpmi: add proper raw access support
Date: Thu, 16 Oct 2014 23:52:52 +0800 [thread overview]
Message-ID: <20141016155247.GA2284@localhost.localdomain> (raw)
In-Reply-To: <EACD232272DA4849B060F0828564D13B44955ABE1F@ntcex01.corp.netcomm.com.au>
On Tue, Oct 14, 2014 at 04:50:27PM +1100, Iwo Mergler wrote:
>
> >
> > No, it doesn't seem to be correct.
> > But it's an MLC flash, so you'll most probably need to apply this patch
> > to nandbiterrs testsuite:
> >
> > http://code.bulix.org/f69wuu-87021
> >
> > This patch is flashing the block between each bitflip insertion to
> > avoid multiple write without erasure (which, AFAIK, is not supported
> > by MLC flashes).
>
> Hi Huang,
>
>
> just out of interest, have you tried this on the MLC NAND without the patch?
yes. I tried. As i posted, it will failed.
>
> I'm aware that MLC says you shouldn't write multiple times, but that is
> with a view towards specified data endurance. I would only expect a few
> additional bit errors during the test.
>
> Did you try the overwrite test?
not yet. I can test it tomorrow.
>
> I'm curious how MLC NAND does when subjected to multiple writes.
We should not do the multiple writes to the MLC nand.
We can do so with the SLC nand.
thank
Huang Shijie
next prev parent reply other threads:[~2014-10-16 15:52 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 14:07 [PATCH v3 0/3] mtd: nand: gpmi: add proper raw access support Boris BREZILLON
2014-09-23 14:07 ` [PATCH v3 1/3] mtd: nand: gpmi: add gpmi_move_bits function Boris BREZILLON
2014-09-23 14:54 ` Huang Shijie
2014-09-23 14:58 ` Boris BREZILLON
2014-09-23 15:04 ` Huang Shijie
2014-09-23 15:20 ` Huang Shijie
2014-09-23 15:25 ` Boris BREZILLON
2014-09-23 14:07 ` [PATCH v3 2/3] mtd: nand: gpmi: add proper raw access support Boris BREZILLON
2014-09-23 15:17 ` Huang Shijie
2014-09-23 15:34 ` Boris BREZILLON
2014-09-23 16:10 ` Huang Shijie
2014-09-23 17:16 ` Boris BREZILLON
2014-09-23 17:21 ` Boris BREZILLON
2014-09-23 14:07 ` [PATCH v3 3/3] mtd: nand: gpmi: add raw oob access functions Boris BREZILLON
2014-09-30 8:07 ` [PATCH v3 0/3] mtd: nand: gpmi: add proper raw access support Boris Brezillon
2014-10-05 2:13 ` Huang Shijie
2014-10-08 14:24 ` Huang Shijie
2014-10-08 15:10 ` Boris Brezillon
2014-10-10 14:42 ` Huang Shijie
2014-10-10 14:53 ` Boris Brezillon
2014-10-14 5:50 ` Iwo Mergler
2014-10-16 15:52 ` Huang Shijie [this message]
2014-10-19 2:20 ` Huang Shijie
2014-10-20 5:02 ` Iwo Mergler
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=20141016155247.GA2284@localhost.localdomain \
--to=shijie8@gmail.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).