Add a parameter that allows you to store the SHA1 sum to either a
memory location or a variable.
Signed-off-by: Joe Hershberger <joe.hershberger@ni.com>
Loosely based on CONFIG_CRC32_VERIFY.
The sum to verify against can be in memory, in a variable, or the last
parameter to the function directly.
Signed-off-by: Joe Hershberger <joe.hershberger@ni.com>
Change all files in common/ to use CMD_RET_USAGE instead of calling
cmd_usage() directly. I'm not completely sure about this patch since
the code since impact is small (100 byte or so on ARM) and it might
need splitting into smaller patches. But for now here it is.
Signed-off-by: Simon Glass <sjg@chromium.org>
* Fix: if using sha1 command watchdog timed out
* change function call sha1_csum(..) to the watchdog-safe variant
sha1_csum_wd(..) to support watchdog reset
Signed-off-by: Jens Scharsig <esw@bus-elektronik.de>
There's no real need to keep these functions in the cmd_mem file since
they do not use any of the common global mem variables. So split them
out into their own dedicated cmd files.
Signed-off-by: Mike Frysinger <vapier@gentoo.org>
Simon Glass
Joe Hershberger
Jens Scharsig
Mike Frysinger