diff options
| author | Rafał Miłecki <zajec5@gmail.com> | 2016-05-06 14:37:05 +0200 |
|---|---|---|
| committer | Rafał Miłecki <zajec5@gmail.com> | 2016-05-09 20:10:58 +0200 |
| commit | df8ca9a5c4d87903ddca15d1a6c60f43b15656fe (patch) | |
| tree | db5d218c753ecf0742bdb961ce27939f39e7aa19 /target/linux/brcm63xx | |
| parent | 2dd125048dedbae3fbad6ae4b89f4b9b6e44b9b1 (diff) | |
| download | upstream-df8ca9a5c4d87903ddca15d1a6c60f43b15656fe.tar.gz upstream-df8ca9a5c4d87903ddca15d1a6c60f43b15656fe.tar.bz2 upstream-df8ca9a5c4d87903ddca15d1a6c60f43b15656fe.zip | |
mtd: add -c option for specifying amount of data to be used for checksum
So far fixtrx was calculating checksum over amount of data matching
partition erase size. It was mostly a workaround of checksum problem
after changing anything in initial TRX content (e.g. formatting JFFS2).
Its main purpose was to make bootloader accept modified TRX. This didn't
provide much protection of flash data against corruption.
This new option lets caller request calculating checksum over a bigger
amount of data. It may be used e.g. to include whole kernel data for
checksum and hopefully make bootloader go info failsafe mode if
something goes wrong.
Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
Diffstat (limited to 'target/linux/brcm63xx')
0 files changed, 0 insertions, 0 deletions