From: Daniel Golle Date: Tue, 6 Jun 2023 00:14:27 +0000 (+0100) Subject: mediatek: set new compat version if booted on R64 and R3 X-Git-Url: http://git.lede-project.org./?a=commitdiff_plain;h=49bd38f01ac6927cda2dc894417994d1256673a7;p=openwrt%2Fstaging%2Fblocktrron.git mediatek: set new compat version if booted on R64 and R3 If the board comes up with OpenWrt that means that the bootloader is recent enough and knows about the new device tree overlays. Using /etc/board.d/ is not enough in this case because it doesn't overwrite existing configuration which may exist (and is fine to exist) if the user updated with 'sysupgrade -F *.itb' and has kept configuration. They would still need to manually set compat_version even though the fact that the bootloader env has been updated can be implied by the fact that the system has started. Hence we can always set compat_version=1.1 for those two boards using uci-defaults. Signed-off-by: Daniel Golle (cherry picked from commit 25e27c4af3f1de872aadbaada434437cba3b0a75) --- diff --git a/target/linux/mediatek/filogic/base-files/etc/uci-defaults/05_fix-compat-version b/target/linux/mediatek/filogic/base-files/etc/uci-defaults/05_fix-compat-version new file mode 100644 index 0000000000..4486f2f090 --- /dev/null +++ b/target/linux/mediatek/filogic/base-files/etc/uci-defaults/05_fix-compat-version @@ -0,0 +1,10 @@ +. /lib/functions.sh + +case "$(board_name)" in + bananapi,bpi-r3) + uci set system.@system[0].compat_version="1.1" + uci commit system + ;; +esac + +exit 0 diff --git a/target/linux/mediatek/mt7622/base-files/etc/uci-defaults/05_fix-compat-version b/target/linux/mediatek/mt7622/base-files/etc/uci-defaults/05_fix-compat-version new file mode 100644 index 0000000000..c77e1cb8bd --- /dev/null +++ b/target/linux/mediatek/mt7622/base-files/etc/uci-defaults/05_fix-compat-version @@ -0,0 +1,10 @@ +. /lib/functions.sh + +case "$(board_name)" in + bananapi,bpi-r64) + uci set system.@system[0].compat_version="1.1" + uci commit system + ;; +esac + +exit 0