aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/archs38
diff options
context:
space:
mode:
authorZoltan HERPAI <wigyori@uid0.hu>2016-07-20 23:51:59 +0200
committerZoltan HERPAI <wigyori@uid0.hu>2016-07-20 23:51:59 +0200
commit246eb4a081a47ac194376225b1929e1b66e90128 (patch)
tree42965c933bdd23df14151fe520731e93a6cb9a3a /target/linux/archs38
parent9afe0c1ec5fa00a1cbdc57ffe23732bf6bc437e6 (diff)
downloadmaster-187ad058-246eb4a081a47ac194376225b1929e1b66e90128.tar.gz
master-187ad058-246eb4a081a47ac194376225b1929e1b66e90128.tar.bz2
master-187ad058-246eb4a081a47ac194376225b1929e1b66e90128.zip
Revert "bcm53xx: use uncompressed zImages"
This reverts commit eab2b26fc4a6263025b3e82870232b0d5bfbc8a3. CFE is known to fail in some non-standard cases, e.g. when using kernel or format different that what was tested by Broadcom. This kernel change triggered some problem with booting OpenWrt kernel stored in Seama. As long as Seama checksum was covering enough data, it was working fine. We need to change it however, because calculating MD5 over part of UBI containing SquashFS is unsafe. UBI may move PEBs depending on flash wearing level which would break CFE booting the image. For some reason this kernel change was breaking CFE. Calculating MD5 over 0x47ffc0 B data or less (there is 0x40 B long header) was stopping booting process at: Starting program at 0x00008000 As our kernel is usually 0x3fffc0 B it was affected by this problem. Reverting this change fixes sysupgrade (which already uses kernel size for MD5 calculation) and will allow us to adjust "fixseama" command call on the first boot. Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
Diffstat (limited to 'target/linux/archs38')
0 files changed, 0 insertions, 0 deletions