crc32: Correct endianness of crc32 result
authorSimon Glass <sjg@chromium.org>
Thu, 18 Apr 2013 10:25:51 +0000 (10:25 +0000)
committerTom Rini <trini@ti.com>
Fri, 19 Apr 2013 14:24:14 +0000 (10:24 -0400)
commit74a18ee8a563d9c21b5856269f911b69bc4aaccb
tree10bd52a8c5b1b855831bb47095ca7819b1d26222
parent2386060c16471f4cd183e6f8bce82450a7574ec6
crc32: Correct endianness of crc32 result

When crc32 is handled by the hash library, it requires the data to be in
big-endian format, since it reads it byte-wise. Thus at present the 'crc32'
command reports incorrect data. For example, previously we might see:

Peach # crc32 40000000 100
CRC32 for 40000000 ... 400000ff ==> 0d968558

but instead with the hash library we see:

Peach # crc32 40000000 100
CRC32 for 40000000 ... 400000ff ==> 5885960d

Correct this.

Signed-off-by: Simon Glass <sjg@chromium.org>
Reviewed-by: Vadim Bendebury <vbendeb@google.com>
lib/crc32.c