dfu: Introduction of the "dfu_checksum_method" env variable for checksum method setting submit/tizen/20140328.090301 submit/tizen/20140328.092950 submit/tizen/20140328.093252 submit/tizen/20140331.085138 submit/tizen_boot/20140328.093938 submit/tizen_boot/20140331.085208 submit/tizen_boot/20140331.110447
authorLukasz Majewski <l.majewski@samsung.com>
Thu, 27 Mar 2014 14:25:05 +0000 (15:25 +0100)
committerLukasz Majewski <l.majewski@samsung.com>
Thu, 27 Mar 2014 14:25:05 +0000 (15:25 +0100)
commitf8d5f05b33418281d0e601786a55afc466c31d89
tree8ce4b3d2610806c5d039a71bc6eb50620e1a5d75
parentd36ae18b9bb26ddf7b8d5c67729d1507526e2e65
dfu: Introduction of the "dfu_checksum_method" env variable for checksum method setting

Up till now the CRC32 of received data was calculated unconditionally.
The standard crc32 implementation causes long delays when large images
were uploaded.

The "dfu_checksum_method" environment variable gives the opportunity to
enable on demand (when e.g. debugging) the crc32 calculation.
It can be done without need to recompile the u-boot binary.

By default the crc32 is not calculated.

Tests results:
400 MiB ums.img file
With  crc32 calculation: 65 sec [avg 6.29 MB/s]
Without  crc32 calculation: 25 sec [avg 16.17 MB/s]

Signed-off-by: Lukasz Majewski <l.majewski@samsung.com>
drivers/dfu/dfu.c
include/dfu.h