diff options
author | Matthias Schiffer <mschiffer@universe-factory.net> | 2018-06-06 20:51:05 +0200 |
---|---|---|
committer | Matthias Schiffer <mschiffer@universe-factory.net> | 2018-06-06 22:27:59 +0200 |
commit | e5301885bc9772f0e5ca5b3870b2c43824e12546 (patch) | |
tree | d85224ce2a2efc766a848702f231563f2412155a /target/linux/ramips | |
parent | 023944853241920c20842c0f4649d1dd4e7e273b (diff) | |
download | upstream-e5301885bc9772f0e5ca5b3870b2c43824e12546.tar.gz upstream-e5301885bc9772f0e5ca5b3870b2c43824e12546.tar.bz2 upstream-e5301885bc9772f0e5ca5b3870b2c43824e12546.zip |
ar71xx: lzma-loader: move padding workaround to gzip step
Some devices (TP-Link TL-WR1043ND v1) don't boot reliably when the
uncompressed loader is too small. This was workarounded in the loader by
adding 512KB of padding to the .data section of the loader binary.
This approach had two issues:
- The padding was only working when .data was non-empty (otherwise the
section would become NOBITS, omitting it in the binary). .data was only
empty when no CMDLINE was set, leading to further workarounds like
fe594bf90d09 ("ath79: fix loader-okli, lzma-loader"), and this
workaround was only effective because a missing "const" led to the kernel
argv being stored in .data instead of .rodata
- The padding was not only added to the compressed .gz loader, but also
uncompressed .bin and .elf loaders. The prevented embedding the kernel
cmdline in the loader for non-gz loader types.
To fix both issues, move the creation of the padding from the linker script
to the gzip step.
Signed-off-by: Matthias Schiffer <mschiffer@universe-factory.net>
Diffstat (limited to 'target/linux/ramips')
0 files changed, 0 insertions, 0 deletions