aboutsummaryrefslogtreecommitdiffstats
path: root/target/linux/ramips/image/lzma-loader
Commit message (Collapse)AuthorAgeFilesLines
* ramips: lzma-loader: make FLASH_START configurableChuanhong Guo2020-09-033-4/+8
| | | | | | | | | | | FLASH_START is supposed to point at the memory area where NOR flash are mapped. We currently have an incorrect FLASH_START copied from ar71xx back then and the loader doesn't work under OKLI mode. On ramips, mt7621 has it's flash mapped to 0x1fc00000 and other SoCs uses 0x1c000000. This commit makes FLASH_START a configurable value to handle both cases. Signed-off-by: Chuanhong Guo <gch981213@gmail.com>
* ramips: Add support for mt7621 to lzma-loaderTobias Schramm2018-06-215-18/+60
| | | | Signed-off-by: Tobias Schramm <tobleminer@gmail.com>
* ramips: lzma-loader: fix O32 ABI conformanceGabor Juhos2016-03-211-0/+3
| | | | | | | | | | | | | | | | | | | According to the calling convention of the o32 ABI the caller function must reserve stack space for $a0-$a3 registers in case the callee needs to save its arguments. The assembly startup code does not reserve stack space for these registers thus when the main C function needs to save its arguments, that will cause a stack overflow. Fix the assembly code to reserve stack space for the registers to avoid that. Untested. It seems that the lzma-loader is not used at all? Signed-off-by: Gabor Juhos <juhosg@openwrt.org> SVN-Revision: 49062
* ralink: update patchesJohn Crispin2013-06-2320-0/+1974
Signed-off-by: John Crispin <blogic@openwrt.org> SVN-Revision: 37016