On Mon, Mar 31, 2014 at 08:15:41PM +0200, Marek Vasut wrote: > On Monday, March 31, 2014 at 08:05:17 PM, Tom Rini wrote: > > On Mon, Mar 31, 2014 at 10:48:49AM +0200, Lukasz Majewski wrote: > > > 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.majew...@samsung.com> > > > > OK, so, protocol question. What's going on in the background here such > > that it's a good and safe idea to not do this checksum and we won't end > > up in the case where data was corrupted and we just bricked a board in > > update mode? > > This is just a convenience measure for people who do a lot of updates > and thus the time matters, it's not a production-feature.
That's what I figured. So we've got the default backwards. -- Tom
signature.asc
Description: Digital signature
_______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
