Simon Glass 74a18ee8a5 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>
2013-04-19 10:24:14 -04:00
..
2012-12-06 13:56:38 -07:00
2012-05-25 09:15:10 +02:00
2012-11-04 11:00:36 -07:00
2012-05-15 08:31:37 +02:00
2010-04-13 09:13:04 +02:00
2010-04-13 09:13:04 +02:00
2010-04-13 09:13:04 +02:00
2010-04-13 09:13:04 +02:00
2010-04-13 09:13:04 +02:00
2010-04-13 09:13:04 +02:00
2010-04-13 09:13:04 +02:00
2011-01-18 23:38:08 +01:00
2010-04-13 09:13:04 +02:00
2010-11-28 21:58:29 +01:00
2010-04-21 23:42:38 +02:00
2010-09-19 19:29:47 +02:00
2012-03-29 08:12:47 +02:00
2012-09-29 07:26:08 -07:00
2010-04-13 09:13:04 +02:00
2010-04-13 09:13:04 +02:00
2012-04-29 14:14:08 +02:00
2010-11-28 21:56:39 +01:00
2012-07-07 14:07:32 +02:00
2010-04-13 09:13:04 +02:00
2012-04-10 23:35:32 +02:00
2013-04-12 14:13:13 -07:00
2013-02-19 17:01:26 -05:00