From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] cmd, nand: add an option to disable the verification when writing in raw mode
Date: Fri, 24 Jun 2016 19:26:44 -0400 [thread overview]
Message-ID: <20160624232644.GJ19080@bill-the-cat> (raw)
In-Reply-To: <1465980138-18496-1-git-send-email-boris.brezillon@free-electrons.com>
On Wed, Jun 15, 2016 at 10:42:18AM +0200, Boris Brezillon wrote:
> Modern NANDs do not guarantee that data written in raw mode will not
> contain bitflips just after writing them. This is fine since the number
> of bitflips should be rather low and thus fixable by the ECC engine,
> but since we are reading data in raw mode to verify if they match the
> input data we cannot prevent failures if some bits are flipped.
>
> The option of using standard mode to verify the data is not acceptable
> either, since one of the usage of raw mode is to allow flashing images
> that do not respect the standard NAND page layout or the default ECC
> config (this is the case on Allwinner platforms, where the ROM code
> tests several hardcoded configs, which are not necessarily matching the
> NAND characteristics).
>
> Add an extension to the nand write.raw command allowing one to disable
> the verification step.
>
> Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
Reviewed-by: Tom Rini <trini@konsulko.com>
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20160624/7f7ca895/attachment.sig>
next prev parent reply other threads:[~2016-06-24 23:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 8:42 [U-Boot] [PATCH] cmd, nand: add an option to disable the verification when writing in raw mode Boris Brezillon
2016-06-24 23:26 ` Tom Rini [this message]
2016-07-25 1:41 ` [U-Boot] " Scott Wood
2016-07-25 9:18 ` Boris Brezillon
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=20160624232644.GJ19080@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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