diff options
| author | Tomasz Maciej Nowak <tomek_n@o2.pl> | 2019-09-17 16:21:51 +0200 |
|---|---|---|
| committer | Christian Lamparter <chunkeey@gmail.com> | 2019-09-21 22:17:39 +0200 |
| commit | 66b7c82bb1767d0c4c1e62ae8051154f182ed2d7 (patch) | |
| tree | 693176f1d0674cba14c079f07e098cb79d945ea8 /target/linux/mvebu | |
| parent | d1e3f32dcf63d19dcfe5cb4a1d8437e7a55cb96e (diff) | |
| download | upstream-66b7c82bb1767d0c4c1e62ae8051154f182ed2d7.tar.gz upstream-66b7c82bb1767d0c4c1e62ae8051154f182ed2d7.tar.bz2 upstream-66b7c82bb1767d0c4c1e62ae8051154f182ed2d7.zip | |
ath79: image: pad kernel for Adtran/Bluesocket devices
It has been reported that using the sysupgrade-tar image will trigger
"lzma_decode failed error". The RedBoot bootloader always loads data
from flash till block size boundary, so if there's no padding it'll also
load the beginning of rootfs, and it seems that lzma_decoder can't handle
that garbage data. Previously the script creating combined-image
silently padded the kernel and rootfs, but since sysupgrade-tar doesn't,
pad the default kernel image.
Fixes: 900330f ("ath79: image: retire combined-image for Adtran/Bluesocket
devices")
Cc: Brian Gonyer <bgonyer@gmail.com>
Cc: Daniel Gimpelevich <daniel@gimpelevich.san-francisco.ca.us>
Signed-off-by: Tomasz Maciej Nowak <tomek_n@o2.pl>
Diffstat (limited to 'target/linux/mvebu')
0 files changed, 0 insertions, 0 deletions