[FS#3492] sysupgrade from CONFIG_MTD_SPI_NOR_USE_4K_SECTORS=y loses settings where image has BLOCKSIZE:=64k

[OpenWrt Bugs]

THIS IS AN AUTOMATED MESSAGE, DO NOT REPLY.

The following task has a new comment added:

FS#3492 - sysupgrade from CONFIG_MTD_SPI_NOR_USE_4K_SECTORS=y loses settings where image has BLOCKSIZE:=64k
User who did this - Roger (rogerpueyo)

----------
>> 2. Tweak mount_root so that it can find the sysupgrade settings
Any ideas on how to implement the second idea, if even possible?

I can answer myself: //using "BLOCKSIZE = 4k" instead of the default 64k when generating the image//. Either on each device entry, or for all the //mikrotik_nor//-type devices. In common-mikrotik.mk:


define Device/mikrotik_nor
  $(Device/mikrotik)
  BLOCKSIZE = 4k
  IMAGE/sysupgrade.bin := append-kernel | kernel2minor -s 1024 -e | \
	pad-to $$$$(BLOCKSIZE) | append-rootfs | pad-rootfs | \
	check-size | append-metadata
endef


Flashing process is still slow, yes, but settings are now kept over upgrades. I tested it on the wAP AC.

@John: What do you think? Would you like to give it a try? Maybe submit a patch?
----------

More information can be found at the following URL:
https://bugs.openwrt.org/index.php?do=details&task_id=3492#comment9932

You are receiving this message because you have requested it from the Flyspray bugtracking system.  If you did not expect this message or don't want to receive mails in future, you can change your notification settings at the URL shown above.