[OpenWrt-Devel] ar71xx Vs ath79 -- sysupgrade

Karl Palsson karlp at tweak.net.au
Fri Dec 7 07:32:35 EST 2018

Henrique de Moraes Holschuh <henrique at nic.br> wrote:
> Em 05/12/2018 21:20, Thomas Endt escreveu:
> >> Auftrag von Henrique de Moraes Holschuh
> >> Do we have a wiki table somewhere that has the device name, ar71xx info
> >> and ath79 info, which could be expanded with ar71xx->ath79 status (no,
> >> yes but unverified, yes verified to be complete)?
> >>
> >> That would be really useful to direct efforts on adding ath79 support
> >> to something that is still ar71xx-only, as well as adding ar71xx->ath79
> >> support to targets of interest (i.e. those one happens to know what
> >> changes are required for the migration, really).
> >>
> >> I suppose one would also add any remarks about ath79 support being
> >> incomplete or any regressions for each target one knows about, too.
> >> That would help steering the ar71xx deprecation.
> > 
> > There is a table that documents the ath79 status in the OpenWrt forum:
> > https://forum.openwrt.org/t/ath79-target-status/18614/9
> > 
> > The place to put this into the wiki would be:
> > https://openwrt.org/docs/techref/targets/ath79
> > 
> > 
> > We can define a new target "ar71xx-ath79" for the dataentries, which would then give us these 3 options:
> > 
> > 1) "ar71xx"          # device is ar71xx only
> > 2) "ath79"           # device is ath79 only
> > 3) "ar71xx-ath79"    # device is migrated (and working, if nothing in "Unsupported Functions")
> > 
> > ---> devices will automatically show up on the ath79 and/or ar71xx wikipage (slight modifications necessary).
> > 
> > For "ath79 WIP" devices, we can set the "Unsupported Functions" datafield (that's where WIP usually is found) to "ath79 WIP, see forum".
> > Any detailed discussion or description of incomplete support should happen elsewhere, i.e. either in the forum or on the respective devicepages.
> > 
> > Please let me know if this meets your requirements.
> Yes, this would do it nicely, provided that we take care to
> describe in the web pages what ar71xx-ath79 means.
> Note that my answer assumes "migrated" (i.e. ar71xx-ath79)
> means the glue to migrate and convert low-level config (LEDs,
> etc) when updating from ar71xx -> ath79 is in place on the
> ath79 port.
> If it just does ar71xx _and_ ath79, BUT one has to manually
> adjust configuration when migrating from ar71xx to ath79, it
> would have to be flagged as WIP or something like that, even if
> all of its functions are fully implemented and working in
> ath79.

One thing we want to avoid meanwhile is keeping the old stuff
"just because" The whole point of moving to ath79 is to be closer
to upstream. If we just go and repatch everythign to make it
compatible with the past, we might as well not have bothered. We
want to make sure that any migrations are migrations to new stuff
_only_ not adapting things to stay in the same place.

Karl P
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.html
Type: application/pgp-signature
Size: 1161 bytes
Desc: OpenPGP Digital Signature
URL: <http://lists.infradead.org/pipermail/openwrt-devel/attachments/20181207/659833a2/attachment.sig>
-------------- next part --------------
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org

More information about the openwrt-devel mailing list