diff options
author | Adrian Schmutzler <freifunk@adrianschmutzler.de> | 2020-07-14 16:11:22 +0200 |
---|---|---|
committer | Adrian Schmutzler <freifunk@adrianschmutzler.de> | 2020-07-31 11:40:15 +0200 |
commit | 494f12c52df6767ec0fabf2b2fac8f453323a4c5 (patch) | |
tree | 2c77be02935442cb9e6b7866000d222d5434d442 /target/linux/kirkwood/base-files | |
parent | 02d6ac1060b4a937adce5912cc22177cac86c318 (diff) | |
download | upstream-494f12c52df6767ec0fabf2b2fac8f453323a4c5.tar.gz upstream-494f12c52df6767ec0fabf2b2fac8f453323a4c5.tar.bz2 upstream-494f12c52df6767ec0fabf2b2fac8f453323a4c5.zip |
mvebu: implement compatibility version for DSA migration
This implements the newly introduced compat-version to prevent
upgrade between swconfig and DSA for mvebu.
Just define a compat version with minor increment and an appropriate
message for both image (in Makefile) and device (in base-files).
Having taken care of sysupgrade, we can put back the SUPPORTED_DEVICES
that have been removed in previous patches to prevent broken config.
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>
Diffstat (limited to 'target/linux/kirkwood/base-files')
0 files changed, 0 insertions, 0 deletions