diff options
| author | markus <markus@3c298f89-4303-0410-b956-a3cf2f4a3e73> | 2010-07-27 15:37:37 +0000 |
|---|---|---|
| committer | markus <markus@3c298f89-4303-0410-b956-a3cf2f4a3e73> | 2010-07-27 15:37:37 +0000 |
| commit | 3c05ba24723fa368dd070c212376b7dbaa4269a6 (patch) | |
| tree | a55f21b7f7bc5cd6bc5ab6545f976b4e155367f8 /target/linux/brcm63xx/patches-2.6.33/140-new_bcm96348gw_leds.patch | |
| parent | dbf130182cf039b11903162e88b063ce4267e8bd (diff) | |
fix CRC32 calculation for sysupgrade
* reduce image size for CRC calculation by fs_mark size
sysupgrade sometimes failed for me and I noticed that it was due
to incorrect CRC values in trx-header after performing it.
It seems that the fs_mark was completely included in the calculation
and that it was nevertheless modified by sysupgrade while appending
the jffs data.
This only occurs for the first boot after sysupgrade as the flashmap
driver recalculates the CRC to an even smaller area when it boots.
git-svn-id: svn://svn.openwrt.org/openwrt/trunk@22396 3c298f89-4303-0410-b956-a3cf2f4a3e73
Diffstat (limited to 'target/linux/brcm63xx/patches-2.6.33/140-new_bcm96348gw_leds.patch')
0 files changed, 0 insertions, 0 deletions