realtek: fix default image generation
While cleaning up the makefiles for the realtek target, the order of the default image generating commands was accidentally changed. This caused the image signature to end up somewhere in the middle, misaligning the rootfs. As a result, sysupgrade couldn't verify upgrade images anymore, and devices end up in a boot loop due to the unaligned (and not found) rootfs. Fixes: 94d8b4852b9f ("realtek: Cleanup Makefiles") Signed-off-by: Sander Vanheule <sander@svanheule.net>
This commit is contained in:
parent
a14170b6e9
commit
ab8a5f2ea0
@ -102,11 +102,11 @@ define Device/Default
|
||||
IMAGES := sysupgrade.bin
|
||||
IMAGE/sysupgrade.bin := \
|
||||
append-kernel | \
|
||||
append-metadata | \
|
||||
pad-to 64k | \
|
||||
append-rootfs | \
|
||||
check-size | \
|
||||
pad-rootfs | \
|
||||
pad-to 64k
|
||||
check-size | \
|
||||
append-metadata
|
||||
endef
|
||||
|
||||
include $(SUBTARGET).mk
|
||||
|
Loading…
x
Reference in New Issue
Block a user