summaryrefslogtreecommitdiff
path: root/cmd/reginfo.c
diff options
context:
space:
mode:
authorBoris Brezillon <boris.brezillon@free-electrons.com>2016-06-15 10:42:18 +0200
committerScott Wood <oss@buserror.net>2016-07-24 20:36:27 -0500
commit2dc3c483a9f7c8215b4523183dc74e8692253404 (patch)
treed8c34e2ee3344b4b93a1968d32cf1bf27dcc16f7 /cmd/reginfo.c
parent29d63a59eaf1c9f3b37e249cda2a97e5e4f183f8 (diff)
downloadu-boot-imx-2dc3c483a9f7c8215b4523183dc74e8692253404.zip
u-boot-imx-2dc3c483a9f7c8215b4523183dc74e8692253404.tar.gz
u-boot-imx-2dc3c483a9f7c8215b4523183dc74e8692253404.tar.bz2
cmd, nand: add an option to disable the verification when writing in raw mode
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>
Diffstat (limited to 'cmd/reginfo.c')
0 files changed, 0 insertions, 0 deletions