aboutsummaryrefslogtreecommitdiffstats
path: root/target
diff options
context:
space:
mode:
authorJohn Crispin <blogic@openwrt.org>2015-06-03 13:58:48 +0000
committerJohn Crispin <blogic@openwrt.org>2015-06-03 13:58:48 +0000
commit9631957f47ba0180e8290e84daa6a6d9f5e0dfb4 (patch)
tree03087561901b8501e9912758fb5ca1b484325d27 /target
parentbf98ea70d66688c54ce035a9f6e3888afa004b9e (diff)
downloadupstream-9631957f47ba0180e8290e84daa6a6d9f5e0dfb4.tar.gz
upstream-9631957f47ba0180e8290e84daa6a6d9f5e0dfb4.tar.bz2
upstream-9631957f47ba0180e8290e84daa6a6d9f5e0dfb4.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> git-svn-id: svn://svn.openwrt.org/openwrt/trunk@45881 3c298f89-4303-0410-b956-a3cf2f4a3e73
Diffstat (limited to 'target')
0 files changed, 0 insertions, 0 deletions