openwrt/target/linux/kirkwood/base-files/etc/board.d/05_compat-version

#
# Copyright (C) 2020 OpenWrt.org
#

. /lib/functions.sh
. /lib/functions/uci-defaults.sh

board_config_update

case "$(board_name)" in
	iom,ix2-200|\
	iom,ix4-200d)
		ucidef_set_compat_version "2.0"
		;;
	linksys,e4200-v2|\
	linksys,ea3500|\
	linksys,ea4500)
		ucidef_set_compat_version "3.0"
		;;
esac

board_config_flush

exit 0
kirkwood: implement compatibility version for DSA migration This implements the newly introduced compat-version to prevent upgrade between swconfig and DSA for kirkwood. Just define a compat version with minor increment and an appropriate message for both image (in Makefile) and device (in base-files). Since we never removed SUPPORTED_DEVICES for this target, we don't have to add it back either. Attention: All users that already updated to the DSA versions in master will receive the same incompatibility warning since their devices are still "1.0" as far as fwtool can tell. Those, and only those, can bypass the upgrade check by using force (-F) without having to reset config again. In addition, the new version string needs to be put into uci config manually, so the new fwtool knows that it actually deals with a "1.1": uci set "system.@system[-1].compat_version=1.1" uci commit system Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> 2020-07-14 16:18:10 +02:00			`#`
			`# Copyright (C) 2020 OpenWrt.org`
			`#`

			`. /lib/functions.sh`
			`. /lib/functions/uci-defaults.sh`

			`board_config_update`

			`case "$(board_name)" in`
kirkwood: resize kernel partition for kirkwood devices The 6.1 kernel has caused another increase in kernel size, and now it's more than 3MB: WARNING: Image file iom_ix4-200d-uImage is too big: 3170394 > 3145728 WARNING: Image file iom_ix2-200-uImage is too big: 3171494 > 3145728 WARNING: Image file linksys_e4200-v2-uImage is too big: 3171879 > 3145728 WARNING: Image file linksys_ea4500-uImage is too big: 3171871 > 3145728 WARNING: Image file linksys_ea3500-uImage is too big: 3171651 > 3145728 This causes problems for 5 devices: - Iomega StorCenter ix2/ix4 - Linksys EA3500/EA4200/EA4500 They have enough resources for proper operation with 6.1, but all of them had a 3MB kernel size limit. Let's keep them alive and resize kernel partitions to 4MB. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com> 2024-03-14 13:57:25 +01:00			`iom,ix2-200\|\`
			`iom,ix4-200d)`
			`ucidef_set_compat_version "2.0"`
			`;;`
kirkwood: use real model names for Linksys devices This replaces the internal device names "Audi" and "Viper" with the real model names, which a user would look for. This makes the Linksys devices on this target consistent with the names recently changed for mvebu based on the same idea. As a consequence, the "viper" device definition is split into two separate definitions with the correct names for both real models. Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> 2020-06-13 00:36:01 +02:00			`linksys,e4200-v2\|\`
			`linksys,ea3500\|\`
			`linksys,ea4500)`
kirkwood: resize kernel partition for kirkwood devices The 6.1 kernel has caused another increase in kernel size, and now it's more than 3MB: WARNING: Image file iom_ix4-200d-uImage is too big: 3170394 > 3145728 WARNING: Image file iom_ix2-200-uImage is too big: 3171494 > 3145728 WARNING: Image file linksys_e4200-v2-uImage is too big: 3171879 > 3145728 WARNING: Image file linksys_ea4500-uImage is too big: 3171871 > 3145728 WARNING: Image file linksys_ea3500-uImage is too big: 3171651 > 3145728 This causes problems for 5 devices: - Iomega StorCenter ix2/ix4 - Linksys EA3500/EA4200/EA4500 They have enough resources for proper operation with 6.1, but all of them had a 3MB kernel size limit. Let's keep them alive and resize kernel partitions to 4MB. Signed-off-by: Pawel Dembicki <paweldembicki@gmail.com> 2024-03-14 13:57:25 +01:00			`ucidef_set_compat_version "3.0"`
kirkwood: implement compatibility version for DSA migration This implements the newly introduced compat-version to prevent upgrade between swconfig and DSA for kirkwood. Just define a compat version with minor increment and an appropriate message for both image (in Makefile) and device (in base-files). Since we never removed SUPPORTED_DEVICES for this target, we don't have to add it back either. Attention: All users that already updated to the DSA versions in master will receive the same incompatibility warning since their devices are still "1.0" as far as fwtool can tell. Those, and only those, can bypass the upgrade check by using force (-F) without having to reset config again. In addition, the new version string needs to be put into uci config manually, so the new fwtool knows that it actually deals with a "1.1": uci set "system.@system[-1].compat_version=1.1" uci commit system Signed-off-by: Adrian Schmutzler <freifunk@adrianschmutzler.de> 2020-07-14 16:18:10 +02:00			`;;`
			`esac`

			`board_config_flush`

			`exit 0`