diff options
author | Thibaut VARÈNE <hacks@slashdirt.org> | 2023-05-05 14:54:03 +0200 |
---|---|---|
committer | Petr Štetiar <ynezz@true.cz> | 2023-05-15 15:35:52 +0200 |
commit | d97143fadc65058754497d8757c0d63fc22b503a (patch) | |
tree | a07329af9d280a871b5152a7716b7c6af71bb6a9 | |
parent | 22ff416483c13ff312e199b0f7c31ffd3d733fc1 (diff) | |
download | upstream-d97143fadc65058754497d8757c0d63fc22b503a.tar.gz upstream-d97143fadc65058754497d8757c0d63fc22b503a.tar.bz2 upstream-d97143fadc65058754497d8757c0d63fc22b503a.zip |
ath79: mikrotik: bump compat version for yafut images
Following 5264296, Mirotik NAND devices now use yafut to flash the
kernel on devices. This method is incompatible with the old-style
"kernel2minor" flash mechanism.
Even though NAND images were disabled in default build since 21.02, a
user flashing a new-style image onto an old-style image would result in
in a soft-brick[1]. In order to prevent such accidental mishap,
especially as these device images will be reenabled in the upcoming
release, bump the compat version.
After the new image is flashed, the compat version can be updated:
uci set system.@system[0].compat_version='1.1'
uci commit
[1] https://github.com/openwrt/openwrt/pull/12225#issuecomment-1517529262
Cc: Michał Kępień <openwrt@kempniu.pl>
Signed-off-by: Thibaut VARÈNE <hacks@slashdirt.org>
Reviewed-by: Robert Marko <robimarko@gmail.com>
-rw-r--r-- | target/linux/ath79/image/common-mikrotik.mk | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/target/linux/ath79/image/common-mikrotik.mk b/target/linux/ath79/image/common-mikrotik.mk index ce349b60b1..b37c8b7197 100644 --- a/target/linux/ath79/image/common-mikrotik.mk +++ b/target/linux/ath79/image/common-mikrotik.mk @@ -18,4 +18,8 @@ endef define Device/mikrotik_nand $(Device/mikrotik) IMAGE/sysupgrade.bin = append-kernel | sysupgrade-tar | append-metadata + DEVICE_COMPAT_MESSAGE := \ + NAND images switched to yafut. If running older image, reinstall from initramfs. + DEVICE_COMPAT_VERSION := 1.1 + endef |