I don't know if it makes any difference, but insofar as there is an AirOS 6.0 now (https://community.ubnt.com/t5/airMAX-Updates-Blog/airOS-6-0-Has-Been-Released/ba-p/1769476) should we change the strong to something like "v7.0.0-" etc.?

On 3/3/2017 7:51 AM, txt.file wrote:
changes the image version from hardcoded OpenWrt to
$VERSION_DIST. AirOS shows a notification with the image version
during a firmware upgrade.

fixes #582

Signed-off-by: Matthias Fritzsche <txt.f...@txtfile.eu>
---
  target/linux/ar71xx/image/ubnt.mk | 6 +++---
  1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/target/linux/ar71xx/image/ubnt.mk 
b/target/linux/ar71xx/image/ubnt.mk
index 7a1fc80..c633ca1 100644
--- a/target/linux/ar71xx/image/ubnt.mk
+++ b/target/linux/ar71xx/image/ubnt.mk
@@ -6,7 +6,7 @@
  # routerboard creates partitions out of the ubnt header
  define Build/mkubntimage
         -$(STAGING_DIR_HOST)/bin/mkfwimage \
-               -B $(UBNT_BOARD) -v 
$(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-OpenWrt-$(REVISION) \
+               -B $(UBNT_BOARD) -v 
$(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-$(VERSION_DIST)-$(REVISION) \
                 -k $(IMAGE_KERNEL) \
                 -r $@ \
                 -o $@
@@ -19,7 +19,7 @@ define Build/mkubntimage-split
         dd if=$@ of=$@.old1 bs=1024k count=1; \
         dd if=$@ of=$@.old2 bs=1024k skip=1; \
         $(STAGING_DIR_HOST)/bin/mkfwimage \
-               -B $(UBNT_BOARD) -v 
$(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-OpenWrt-$(REVISION) \
+               -B $(UBNT_BOARD) -v 
$(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-$(VERSION_DIST)-$(REVISION) \
                 -k $@.old1 \
                 -r $@.old2 \
                 -o $@; \
@@ -28,7 +28,7 @@ endef
define Build/mkubntimage2
         -$(STAGING_DIR_HOST)/bin/mkfwimage2 -f 0x9f000000 \
-               -v $(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-OpenWrt-$(REVISION) \
+               -v $(UBNT_TYPE).$(UBNT_CHIP).v6.0.0-$(VERSION_DIST)-$(REVISION) 
\
                 -p jffs2:0x50000:0xf60000:0:0:$@ \
                 -o $@.new
         @mv $@.new $@


_______________________________________________
Lede-dev mailing list
Lede-dev@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/lede-dev

Reply via email to