diff options
| author | Chuanhong Guo <gch981213@gmail.com> | 2020-09-02 14:22:29 +0800 |
|---|---|---|
| committer | Adrian Schmutzler <freifunk@adrianschmutzler.de> | 2020-09-03 14:15:30 +0200 |
| commit | cac9e3e2cb2327442406645b261f2861c2263cd5 (patch) | |
| tree | 80b3dddaa0efbf9dc1250df41d7b52e9fe44d99e /target/linux/ramips/image/lzma-loader/Makefile | |
| parent | 7a5e4f5f0090ab257815d890964562debae0a6a9 (diff) | |
| download | upstream-cac9e3e2cb2327442406645b261f2861c2263cd5.tar.gz upstream-cac9e3e2cb2327442406645b261f2861c2263cd5.tar.bz2 upstream-cac9e3e2cb2327442406645b261f2861c2263cd5.zip | |
ramips: lzma-loader: make FLASH_START configurable
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>
Diffstat (limited to 'target/linux/ramips/image/lzma-loader/Makefile')
| -rw-r--r-- | target/linux/ramips/image/lzma-loader/Makefile | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/target/linux/ramips/image/lzma-loader/Makefile b/target/linux/ramips/image/lzma-loader/Makefile index f22151c9d7..4cf700d8c6 100644 --- a/target/linux/ramips/image/lzma-loader/Makefile +++ b/target/linux/ramips/image/lzma-loader/Makefile @@ -13,6 +13,7 @@ LOADER := loader.bin LOADER_NAME := $(basename $(notdir $(LOADER))) LOADER_DATA := TARGET_DIR := +FLASH_START := FLASH_OFFS := FLASH_MAX := BOARD := @@ -40,6 +41,7 @@ loader-compile: $(PKG_BUILD_DIR)/.prepared $(MAKE) -C $(PKG_BUILD_DIR) CROSS_COMPILE="$(TARGET_CROSS)" \ LZMA_TEXT_START=$(LZMA_TEXT_START) \ LOADER_DATA=$(LOADER_DATA) \ + FLASH_START=$(FLASH_START) \ FLASH_OFFS=$(FLASH_OFFS) \ FLASH_MAX=$(FLASH_MAX) \ BOARD="$(BOARD)" \ |