ath79: sysupgrade format policy for ar71xx migrations

[Sven Eckelmann]

On Tuesday, 24 November 2020 08:58:04 CET Sven Eckelmann wrote:
[...]
> Now to the actual question:

I will just add some extra info to the options shown below. Maybe it makes 
then more sense why I've added two gluon developers to the Cc.

> What should the OpenMesh devices use as images for ath79:
> 
> 1. CE01 factory + sysupgrade-tar (like the OpenMesh IPQ40xx devices)

This would say this makes definitely sense for new devices. But in freifunk-
gluon's context, this would mean that the autoupdater cannot automatically 
upgrade from ar71xx to ath79.

So if this is preferred, then there is at least a manual way to upgrade a 
freifunk-gluon node to ath79. And this would be a "good" opportunity to get 
rid of the CE01 upgrade code.

But maybe there is also a solution for this in gluon's context. David and 
Matthias might know more about this.

> 2. CE01 factory + CE01 sysupgrade (like ar71xx)

At the moment, I would rather drop the factory image and not use this option. 
This would (in my eyes) only be necessary when some tools are not able to deal 
with the metadata at the end of the sysupgrade image.

> 3. CE01 sysupgrade (like ar71xx but avoid having two files with the same 
>    content)

With this option, we would (hopefully) have a clean upgrade path with 
freifunk-gluon's autoupdater. The dualboot_datachk sysupgrade code can be 
adjusted to just work with CE01 images by creating some kind of hybrid between 
the old upgrade/openmesh.sh and the new upgrade/dualboot_datachk.sh. Or the 
old upgrade/openmesh.sh (minus some unnecessary steps) can just be reused.

Kind regards,
	Sven
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.openwrt.org/pipermail/openwrt-devel/attachments/20201125/17d8a574/attachment-0001.sig>