aboutsummaryrefslogtreecommitdiffstats
path: root/target
diff options
context:
space:
mode:
authorJohn Crispin <john@openwrt.org>2015-06-03 13:58:48 +0000
committerJohn Crispin <john@openwrt.org>2015-06-03 13:58:48 +0000
commit5d3f0eea1c2ff9e72ba9c2a750e45e915e9bae52 (patch)
treec07493925b66ca3edc8da35ec72849c0f1ccc73f /target
parentf9f093baa33cb747d511f741cae514307a0671f4 (diff)
downloadupstream-5d3f0eea1c2ff9e72ba9c2a750e45e915e9bae52.tar.gz
upstream-5d3f0eea1c2ff9e72ba9c2a750e45e915e9bae52.tar.bz2
upstream-5d3f0eea1c2ff9e72ba9c2a750e45e915e9bae52.zip
tools/firmware-utils: Allow changing the CRC32 poly value in mkbrnimg
VGV7519 is currently the only device with brnboot support. It seems to be happy with 0x2083b8ed as CRC32 poly. However, VGV7510KW22 fails to validate the checksum - it requires 0x04c11db7 instead. I have built an brnboot image manually on the command line, once with the old code and then with the new code but passing the old CRC32 poly value. Both resulted in a brnboot image with the same sha1sum. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 45881
Diffstat (limited to 'target')
0 files changed, 0 insertions, 0 deletions