Home
last modified time | relevance | path

Searched hist:"352 ef3f1b613cb711c51ec962d2cc1eafff1bf95" (Results 1 – 2 of 2) sorted by relevance

/openbmc/u-boot/common/
H A Dflash.c352ef3f1b613cb711c51ec962d2cc1eafff1bf95 Thu Apr 04 08:53:14 CDT 2013 Stefan Roese <sr@denx.de> flash: Add optional verify-after-write feature

Sometimes it might make sense to verify the written data to NOR flash.
This patch adds this feature. To enable this verify-after-write, you
need to define CONFIG_FLASH_VERIFY in your board config header.

Please note that this option is useless in nearly all cases,
since such flash programming errors usually are detected earlier
while unprotecting/erasing/programming. Please only enable
this option if you really know what you are doing.

Signed-off-by: Stefan Roese <sr@denx.de>
/openbmc/u-boot/
H A DREADME352ef3f1b613cb711c51ec962d2cc1eafff1bf95 Thu Apr 04 08:53:14 CDT 2013 Stefan Roese <sr@denx.de> flash: Add optional verify-after-write feature

Sometimes it might make sense to verify the written data to NOR flash.
This patch adds this feature. To enable this verify-after-write, you
need to define CONFIG_FLASH_VERIFY in your board config header.

Please note that this option is useless in nearly all cases,
since such flash programming errors usually are detected earlier
while unprotecting/erasing/programming. Please only enable
this option if you really know what you are doing.

Signed-off-by: Stefan Roese <sr@denx.de>