diff options
| author | Jonas Jelonek | 2025-12-22 09:57:52 +0000 |
|---|---|---|
| committer | Hauke Mehrtens | 2025-12-22 23:26:35 +0000 |
| commit | 74b5a63cf954219289e35a00d70eb09355b5d5ec (patch) | |
| tree | abf20ee653e2b9151ee39b9b09dbb64c6d642049 | |
| parent | b1c1b713f004a74a0138c6f67851c39ce1038112 (diff) | |
| download | openwrt-74b5a63cf954219289e35a00d70eb09355b5d5ec.tar.gz | |
realtek: image: add rt-loader-no-uimage recipe
Add a new recipe 'rt-loader-no-uimage' that passes the kernel load
address to rt-loader, causing it to use that instead of it's initial run
address.
The usual behavior is fine for uImages where the load address is
predefined in the header, U-boot loads the image to that address and
then runs it, rt-loader just takes over that address. For non-uImage
instead, the address is tightly coupled to where the image has been
transferred during serial or TFTP upload. This may not be possible on
several devices. Passing a separate kernel load address to rt-loader
decouples that and avoids taking the pain to change the load address of
the kernel itself.
Signed-off-by: Jonas Jelonek <jelonek.jonas@gmail.com>
Link: https://github.com/openwrt/openwrt/pull/21248
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
| -rw-r--r-- | target/linux/realtek/image/Makefile | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/target/linux/realtek/image/Makefile b/target/linux/realtek/image/Makefile index 786dd12710..db1776340e 100644 --- a/target/linux/realtek/image/Makefile +++ b/target/linux/realtek/image/Makefile @@ -30,6 +30,13 @@ define Build/rt-loader mv "$@.new" "$@" endef +define Build/rt-loader-no-uimage + $(MAKE) all clean -C rt-loader CROSS_COMPILE="$(TARGET_CROSS)" \ + KERNEL_ADDR="$(KERNEL_LOADADDR)" KERNEL_IMG_IN="$@" \ + KERNEL_IMG_OUT="$@.new" BUILD_DIR="$@.build" + mv "$@.new" "$@" +endef + define Build/zyxel-vers ( echo VERS;\ for hw in $(ZYXEL_VERS); do\ |