[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20141016155247.GA2284@localhost.localdomain>
Date: Thu, 16 Oct 2014 23:52:52 +0800
From: Huang Shijie <shijie8@...il.com>
To: Iwo Mergler <Iwo.Mergler@...commwireless.com>
Cc: Boris Brezillon <boris.brezillon@...e-electrons.com>,
Mike Voytovich <mvoytovich@...pal.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"linux-mtd@...ts.infradead.org" <linux-mtd@...ts.infradead.org>,
Roy Lee <roylee@...pal.com>,
Brian Norris <computersforpeace@...il.com>,
David Woodhouse <dwmw2@...radead.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v3 0/3] mtd: nand: gpmi: add proper raw access support
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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists