Safeloader firmware images contain a soft-version partition, which encodes version info about the image. There are currently two formats: plain text and structured binary with the firmware version number and build info.
Currently custom firmware version number values can only be provided if these are text based. However, some device firmwares expect structured binary version info, and do not support the plain text format. The first patch implements a more flexible soft-version override system. The second patch then changes the (structured) soft-version override for the EAP235-WALL v1 to support recent vendor firmwares. EAP235-Wall support will be included in the 21.02 release, but users who have a v3 (or later) firmware installed, will not be able to install those images due to OpenWrt's "0.0.0" soft-version. Eiter both patches need to be included in 21.02, or users need to first install a snapshot image before they can install a 21.02 release image. How would PKG_RELEASE conflicts be avoided for backported patches? Sander Vanheule (2): firmware-utils: tplink-safeloader: improve soft-version customisation firmware-utils: tplink-safeloader: set EAP235-Wall v1 soft-version tools/firmware-utils/Makefile | 2 +- tools/firmware-utils/src/tplink-safeloader.c | 165 +++++++++++-------- 2 files changed, 94 insertions(+), 73 deletions(-) -- 2.31.1 _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/mailman/listinfo/openwrt-devel