25 Nov
2013
25 Nov
'13
10:56 p.m.
On Thu, Nov 07, 2013 at 07:39:48AM -0500, Tom Rini wrote:
In the case of not having CONFIG_CMD_HASH but having CONFIG_CMD_CRC32 enabled (and not CONFIG_CRC32_VERIFY), we end up in this part of the code path on hash_command(). However, we will only have exactly 3 args here, and 3 > 3 is false, and we will not try and store the hash at the address given as arg #3. The next problem however is that we've been moving argv around so the third value is now in argv[0] not argv[3].
Confirmed on AM335x Beaglebone White.
Signed-off-by: Tom Rini trini@ti.com
Applied to u-boot/master, thanks!
--
Tom