diff options
author | Nick Hainke <vincent@systemli.org> | 2021-12-26 11:59:44 +0100 |
---|---|---|
committer | David Bauer <mail@david-bauer.net> | 2021-12-27 03:07:22 +0100 |
commit | cfa670bf16afc10855ca0adec50a807b684ba6a7 (patch) | |
tree | 21630b9649eeaf99ebf5249cef7fe85778bc5bc3 /target/linux/ath79/patches-5.4/408-mtd-redboot_partition_scan.patch | |
parent | 0dc4ab344bf52fce60128f0d710b88150ed47507 (diff) | |
download | upstream-cfa670bf16afc10855ca0adec50a807b684ba6a7.tar.gz upstream-cfa670bf16afc10855ca0adec50a807b684ba6a7.tar.bz2 upstream-cfa670bf16afc10855ca0adec50a807b684ba6a7.zip |
ath79: add missing UBNT_REVISION
The UBNT_REVISION was already added for the ubnt-xw target because:
U-boot bootloader on M-XW devices expects factory image revision
version in specific format. On airOS v6.1.7 with `U-Boot 1.1.4-s1039
(May 24 2017 - 15:58:18)` bootloader checks if the revision major(?)
number is actually a number, but in currently generated images there's
OpenWrt text and so the check fails
...
By placing arbitrary correct number first in major version, we make the
bootloader happy and we can flash factory images over TFTP again.
commit d42a7c469909 ("ath79: ubnt-m-xw: Fix factory image flashing using TFTP recovery method")
Fixes errors in the form of (tftp flashing):
sent DATA <block=8577, 412 bytes>
received ERROR <code=2, msg=Firmware check failed>
Error code 2: Firmware check failed
The missing UBNT_REVISION was not noticed before, since the
UBNT_REVISION field for the ubnt-xm target was also set to:
"42.OpenWrt-..."
Probably, UBNT_REVISION for the ubnt-xm target was set by the ubnt-xw
and was never overridden somewhere else. However, it is missing and
should be part of the ubnt-xm device.
Signed-off-by: Nick Hainke <vincent@systemli.org>
Diffstat (limited to 'target/linux/ath79/patches-5.4/408-mtd-redboot_partition_scan.patch')
0 files changed, 0 insertions, 0 deletions