ar71xx - ath79 migration progress

[AiyionPrime]

@NeoRaider's recent contribution of the network regeneration got merged (thanks to all involved!) and if I'm not mistaken, we've agreed on testing the devices that were gone again, as if we'd be adding new support for them.

That's arguably an effort, but hopefully one divided on several shoulders.

Below is a list of devices that got dropped with the target ar71xx, which hadn't been marked as tiny back then and was not within the mikrotik subtarget. I think that would be a solid start for the migration.

I'll order them in ongoing, todo and done. Please sue ctrl+f to find the device you are interested in.

Testing the devices is not only flashing from stock and via sysupgrade, but sysupgrading from an old ar71xx image as well. You do not need to build an ar71xx image for this, as hanover has them available here and will provide you with access to its VPN infrastructure. If possible let us know when you're done with the key.

Testing will result in failures for some devices due to unhandled migrations for now.

Thanks for your help, Aiyion.

in progress

subtarget	tester	PR	device

todo

@rotanid just showed me a (shorter?) list of devices to migrate, which includes tiny targets as well. I extracted the parts, where someone announced he would be willing to test the device. For now I wont update from that list on a regular basis, but just this once. If somebody wants to test a device, submit a PR draft to gluon and I'll update this accordingly. Thanks for the hint.

subtarget	wanted to test	devices	device
generic			8devices-carambola2-board
generic			allnet-all0315
generic	Nordmann		buffalo-wzr-hp-g300nh2
generic			buffalo-wzr-hp-g450h
generic			gl-inet-6408a-v1
generic			meraki-mr12 (was broken)
generic			meraki-mr16 (was broken)
generic	Gütersloh		netgear-wndrmacv2
generic			netgear-wndrmac
generic			tp-link-archer-c60-v2 (was broken)
generic	@mweinelt, @blocktrron		tp-link-tl-wr2543n-nd-v1
generic			ubiquiti-rocket-m2-ti
generic			ubiquiti-rocket-m2-xw
generic			ubiquiti-rocket-m5-ti
generic			ubiquiti-rocket-m5-xw
generic			ubiquiti-rocket-m-ti
generic			ubiquiti-rocket-m-xw
generic	@AiyionPrime		ubiquiti-unifiap-outdoor
generic			wd-my-net-n600
generic			wd-my-net-n750
generic	@achterin, Nordmann	#2460	zyxel-nbg6616
nand	@belzebub40k knows a tester and provided that person with images		zyxel-nbg6716

done

subtarget	tester	PR	device
generic	@T-X	#2583	alfa-network-ap121f
generic	@Dark4MD	#2435	avm-fritz-box-4020
generic	@ambassador86	#2406	avm-fritz-wlan-repeater-300e
generic	@AiyionPrime	#2420	avm-fritz-wlan-repeater-450e
generic	follow-up		buffalo-wzr-600dhp
generic	@ce-4	#2515	buffalo-wzr-hp-ag300h
generic	@kpanic23	#2551	buffalo-wzr-hp-g300nh(-s)
generic	@s-2	#2417	d-link-dap-1330-rev-a1
generic	@s-2	#2524	d-link-dir-825-rev-b1
generic	@rotanid	#2453	gl-inet-6416a-v1
generic	@AiyionPrime	#2441	gl.inet-gl-ar150
generic	@rotanid	#2455	gl.inet-gl-ar300m
generic	@rotanid	#2454	gl.inet-gl-ar750
generic	@rotanid	#2476	gl.inet-gl-usb150
generic	@rotanid	#2482	netgear-wndr3700
generic	@rabbit83ka	#2485	netgear-wndr3700v2
nand	@gRaSmOnStEr	#2523	netgear-wndr3700v4
generic	@blocktrron	#2586	netgear-wndr3800
generic	@blocktrron	#2586	netgear-wndr3800chmychart
nand	@AiyionPrime	#2554	netgear-wndr4300
generic	@ce-4	#2582	netgear-wnr2200 (was untested)
generic	@blocktrron	#2606	ocedo-koala
generic	@ecsv	#2325	openmesh-a40
generic	@ecsv	#2325	openmesh-a60
generic	@ecsv	#2325	openmesh-mr1750
generic	@ecsv	#2325	openmesh-mr1750v2
generic	@ecsv	#2325	openmesh-mr600
generic	@ecsv	#2325	openmesh-mr600v2
generic	@ecsv	#2325	openmesh-mr900
generic	@ecsv	#2325	openmesh-mr900v2
generic	@ecsv	#2325	openmesh-om2p
generic	@ecsv	#2325	openmesh-om2pv2
generic	@ecsv	#2325	openmesh-om2pv4
generic	@ecsv	#2325	openmesh-om2p-hs
generic	@ecsv	#2325	openmesh-om2p-hsv2
generic	@ecsv	#2325	openmesh-om2p-hsv3
generic	@ecsv	#2325	openmesh-om2p-hsv4
generic	@ecsv	#2325	openmesh-om2p-lc
generic	@ecsv	#2325	openmesh-om5p
generic	@ecsv	#2325	openmesh-om5p-ac
generic	@ecsv	#2325	openmesh-om5p-acv2
generic	@ecsv	#2325	openmesh-om5p-an
generic	@AiyionPrime	#2306	onion-omega
generic	@rotanid	#2477	tp-link-archer-c25-v1 (was broken)
generic	@AiyionPrime	#2427	tp-link-archer-c5-v1
generic	@moridius	#2521	tp-link-archer-c58-v1 (was broken)
generic	@rotanid	#2489	tp-link-archer-c59-v1
generic	@AiyionPrime	#2496	tp-link-archer-c60-v1 (was broken)
generic	@Dark4MD	#2437	tp-link-archer-c7-v2
generic	@AiyionPrime	#2497	tp-link-archer-c7-v4
generic	@Dark4MD	#2436	tp-link-archer-c7-v5
generic	@AiyionPrime	#2410	tp-link-cpe210-v1
generic	@AiyionPrime	#2410	tp-link-cpe210-v1.0
generic	@AiyionPrime	#2410	tp-link-cpe210-v1.1
generic	@AiyionPrime	#2429	tp-link-cpe210-v2
generic	@AiyionPrime	#2429	tp-link-cpe210-v2.0
generic	@moridius	#2506	tp-link-cpe210-v3
generic	@moridius	#2506	tp-link-cpe210-v3.0
generic	@moridius	#2506	tp-link-cpe210-v3.1
generic	@moridius	#2506	tp-link-cpe210-v3.20
generic	@AiyionPrime	#2430	tp-link-cpe510-v1
generic	@AiyionPrime	#2430	tp-link-cpe510-v1.0
generic	@AiyionPrime	#2430	tp-link-cpe510-v1.1
generic	follow-up		tp-link-re355 (was broken)
generic	"Dionys"	#2581	tp-link-re450 (was broken)
generic	@rotanid	#2450	tp-link-tl-wdr3500-v1
generic	@neoraider	#2288	tp-link-tl-wdr3600-v1
generic	@neoraider	#2288	tp-link-tl-wdr4300-v1
generic	@rotanid	#2451	tp-link-tl-wr842n-nd-v3
generic	@rotanid	#2452	tp-link-tl-wr1043n-nd-v2
generic	@AiyionPrime	#2415	tp-link-tl-wr1043n-nd-v3
generic	@AiyionPrime	#2431	tp-link-tl-wr1043n-nd-v4
generic	@herbetom	#2483	tp-link-tl-wr1043n-v5
generic	@Dark4MD	#2442	tp-link-tl-wr810n-v1
generic	@Dark4MD	#2546	tp-link-tl-wr902ac-v1 (was broken)
generic	followup	#2461	tp-link-wbs210-v1
generic	@rotanid	#2461	tp-link-wbs210-v1.20
generic	@dk8hc	#2543	tp-link-wbs510-v1
generic	follow-up		tp-link-wbs510-v1.20
generic	follow-up	210	ubiquiti-loco-m-xw
generic	@AiyionPrime	#2432	ubiquiti-nanobeam-m5 (was untested)
generic	"nordm4nn"	#2547	ubiquiti-nanostation-loco-m2-xw
generic	@Noodlesalat	#2562	ubiquiti-nanostation-loco-m5-xw
generic	virtual	#2443	ubiquiti-nanostation-m-xw
generic	followup	#2443	ubiquiti-nanostation-m2-xw
generic	@AiyionPrime	#2443	ubiquiti-nanostation-m5-xw
generic	follow-up	#2580	ubiquiti-rocket-m
generic	@nrbffs	#2580	ubiquiti-rocket-m2
generic	follow-up	#2580	ubiquiti-rocket-m5
generic	@AiyionPrime	#2421	ubiquiti-unifi
generic	follow-up	#2448	ubiquiti-unifi-ac-lite
generic	follow-up	#2448	ubiquiti-unifi-ac-lr
generic	@AiyionPrime	#2428	ubiquiti-unifi-ac-mesh
generic	@nrbffs	#2462	ubiquiti-unifi-ac-mesh-pro
generic	@Dark4MD	#2439	ubiquiti-unifi-ac-pro
generic	@AiyionPrime	#2421	ubiquiti-unifi-ap
generic	@AiyionPrime	#2421	ubiquiti-unifi-ap-lr
generic	@neoraider	#2440	ubiquiti-unifi-ap-outdoor+
generic	@AiyionPrime	#2416	ubiquiti-unifi-ap-pro

unlikely/wontfix

subtarget	reason	PR	device
nand	upstream tar sysupgrade needs fixing	#2552	aerohive-hiveap-121
generic	never sold		tp-link-cpe220-v1
generic	never sold		tp-link-cpe220-v1.1
generic	never sold		tp-link-cpe520-v1.1

as tasklist for actual progress tracking

in progress

todo

• [ ] 8devices-carambola2-board
• [ ] allnet-all0315
• [ ] buffalo-wzr-hp-g300nh2
• [ ] buffalo-wzr-hp-g450h
• [ ] gl-inet-6408a-v1
• [ ] meraki-mr12 (was broken)
• [ ] meraki-mr16 (was broken)
• [ ] netgear-wndrmacv2
• [ ] netgear-wndrmac
• [ ] tp-link-archer-c60-v2 was broken
• [ ] tp-link-tl-wr2543n-nd-v1
• [ ] ubiquiti-rocket-m2-ti
• [ ] ubiquiti-rocket-m2-xw
• [ ] ubiquiti-rocket-m5-ti
• [ ] ubiquiti-rocket-m5-xw
• [ ] ubiquiti-rocket-m-ti
• [ ] ubiquiti-rocket-m-xw
• [ ] ubiquiti-unifiap-outdoor
• [ ] wd-my-net-n600
• [ ] wd-my-net-n750
• [ ] zyxel-nbg6616
• [ ] zyxel-nbg6716

done

• [x] alfa-network-ap121f
• [x] avm-fritz-box-4020
• [x] avm-fritz-wlan-repeater-300e
• [x] avm-fritz-wlan-repeater-450e
• [x] buffalo-wzr-600dhp
• [x] buffalo-wzr-hp-ag300h
• [x] buffalo-wzr-hp-g300nh
• [x] d-link-dap-1330-rev-a1
• [x] d-link-dir-505-rev-a1
• [x] d-link-dir-505-rev-a2
• [x] d-link-dir-825-rev-b1
• [x] gl-inet-6416a-v1
• [x] gl.inet-gl-ar150
• [x] gl.inet-gl-ar300m
• [x] gl.inet-gl-ar750
• [x] gl.inet-gl-usb150
• [x] netgear-wndr3700
• [x] netgear-wndr3700v2
• [x] netgear-wndr3700v4
• [x] netgear-wndr3800
• [x] netgear-wndr3800chmychart
• [x] netgear-wndr4300
• [x] netgear-wnr2200 (was untested)
• [x] ocedo-koala
• [x] onion-omega (was broken)
• [x] openmesh-a40
• [x] openmesh-a60
• [x] openmesh-mr1750
• [x] openmesh-mr1750v2
• [x] openmesh-mr600
• [x] openmesh-mr600v2
• [x] openmesh-mr900
• [x] openmesh-mr900v2
• [x] openmesh-om2p
• [x] openmesh-om2pv2
• [x] openmesh-om2pv4
• [x] openmesh-om2p-hs
• [x] openmesh-om2p-hsv2
• [x] openmesh-om2p-hsv3
• [x] openmesh-om2p-hsv4
• [x] openmesh-om2p-lc
• [x] openmesh-om5p
• [x] openmesh-om5p-ac
• [x] openmesh-om5p-acv2
• [x] openmesh-om5p-an
• [x] tp-link-archer-c25-v1 was broken
• [x] tp-link-archer-c5-v1
• [x] tp-link-archer-c58-v1 was broken
• [x] tp-link-archer-c59-v1
• [x] tp-link-archer-c60-v1 was broken
• [x] tp-link-archer-c7-v2
• [x] tp-link-archer-c7-v4
• [x] tp-link-archer-c7-v5
• [x] tp-link-cpe210-v1
• [x] tp-link-cpe210-v1.0
• [x] tp-link-cpe210-v1.1
• [x] tp-link-cpe210-v2
• [x] tp-link-cpe210-v2.0
• [x] tp-link-cpe210-v3
• [x] tp-link-cpe210-v3.0
• [x] tp-link-cpe210-v3.1
• [x] tp-link-cpe210-v3.20
• [x] tp-link-cpe510-v1
• [x] tp-link-cpe510-v1.0
• [x] tp-link-cpe510-v1.1
• [x] tp-link-re355 was broken
• [x] tp-link-re450 was broken
• [x] tp-link-tl-wdr3500-v1
• [x] tp-link-tl-wdr3600-v1
• [x] tp-link-tl-wdr4300-v1
• [x] tp-link-tl-wr1043n-nd-v2
• [x] tp-link-tl-wr1043n-nd-v3
• [x] tp-link-tl-wr1043n-nd-v4
• [x] tp-link-tl-wr1043n-v5
• [x] tp-link-tl-wr810n-v1
• [x] tp-link-tl-wr842n-nd-v3
• [x] tp-link-tl-wr902ac-v1 was broken
• [x] tp-link-wbs210-v1
• [x] tp-link-wbs210-v1.20
• [x] tp-link-wbs510-v1
• [x] tp-link-wbs510-v1.20
• [x] ubiquiti-loco-m-xw
• [x] ubiquiti-nanobeam-m5 (was untested)
• [x] ubiquiti-nanostation-loco-m2-xw
• [x] ubiquiti-nanostation-loco-m5-xw
• [x] ubiquiti-nanostation-m-xw
• [x] ubiquiti-nanostation-m2-xw
• [x] ubiquiti-nanostation-m5-xw
• [x] ubiquiti-rocket-m
• [x] ubiquiti-rocket-m2
• [x] ubiquiti-rocket-m5
• [x] ubiquiti-unifi
• [x] ubiquiti-unifi-ac-lite
• [x] ubiquiti-unifi-ac-lr
• [x] ubiquiti-unifi-ac-mesh
• [x] ubiquiti-unifi-ac-mesh-pro
• [x] ubiquiti-unifi-ac-pro
• [x] ubiquiti-unifi-ap
• [x] ubiquiti-unifi-ap-lr
• [x] ubiquiti-unifi-ap-outdoor+
• [x] ubiquiti-unifi-ap-pro

wontfix

• aerohive-hiveap-121
• tp-link-cpe220-v1
• tp-link-cpe220-v1.1
• tp-link-cpe520-v1.1

[s-2]

I will take care of d-link-dap-1330-rev-a1 and d-link-dir-505-rev-a1 (maybe also a2 if I happen to find a unit within my pile, though I believe they are identical except for the exchangeable mains plug).

What happened to DIR-825 B1? It should still have sufficient memory and is supported in OpenWrt ath79, maybe I can still find a unit as well.

[AiyionPrime]

@s-2 I'll add your efforts to the list above, once you drafted the PRs for the respective devices.

Regarding DIR-825 B1, it's has only 6M for firmware and has been marked as tiny before in https://github.com/freifunk-gluon/gluon/commit/cfce3ee91e17708df44331b45f7b80cb6256b458.

~~Feel free to try, but tiny is out of scope for this tracker, as I wrote above.~~

[neocturne]

I can also take care of the tp-link-archer-c7-v2.

[Dark4MD]

I can also take care of the tp-link-archer-c7-v2.

i have it nearly finished, just waiting for a new build to finish because i was missing to add the wifi driver and if that works i post the PR.

[heis2201]

Hi @AiyionPrime , I got your DM on https://forum.freifunk.net/, feel free to use my github account @heis2201.

I am happy to contribute by testing the migration process, however, I need to find some spare time and I have to figure out how to flash the OEM firmware back onto the tp-link-tl-wdr3500-v1.

Is there is chance I can brick the device to a state where recovery is impossible? Did I get this right that test migration of each device is documented in a separate issue here on github?

Cheers

[rotanid]

@AiyionPrime what does "wants to test" in your list mean? the text above suggests that this person intends to create a PR, which is not the same as testing something. i don't have the time to create PRs for all the devices mentioning my name. also, i don't have a C59 and a wr1043v5 at the moment to test, but i have a ubiquiti-unifi-ac-lr also note, ubiquiti-unifi-ac-mesh is no separate device but an alias, as far as i know.

[neocturne]

also note, ubiquiti-unifi-ac-mesh is no separate device but an alias, as far as i know.

It's a separate device in ath79. As no dynamic model detection exists anymore, even completely identical devices get separate images, so each can show the correct model name.

[AiyionPrime]

Hi @AiyionPrime , I got your DM on https://forum.freifunk.net/, feel free to use my github account @heis2201.

Nice, I'll update the list accordingly.

I am happy to contribute by testing the migration process, however, I need to find some spare time and I have to figure out how to flash the OEM firmware back onto the tp-link-tl-wdr3500-v1.

Is there is chance I can brick the device to a state where recovery is impossible?

The OpenWrt page is worth a visit, when it comes to sharing experiences with flashing in various directions. While it should not happen, it's technically possible to brick your device. Most devices do have some form of recovery though, which OpenWrt (and therefore gluon as well) aim not to overwrite.

If you are uncomfortable doing the testing alone, you can always ask for help in hackint#gluon, there are enough people who have done the same process before.

Did I get this right that test migration of each device is documented in a separate issue here on github?

That I try to open a seperate PR for every device I add helps me to stay on top of what I'm doing, when I work on five different devices. There's no rule you cannot do more that one device at once, which @ecsv impressively demonstrated a week ago :D It just keeps things simple.

[AiyionPrime]

@AiyionPrime what does "wants to test" in your list mean? the text above suggests that this person intends to create a PR, which is not the same as testing something. i don't have the time to create PRs for all the devices mentioning my name. also, i don't have a C59 and a wr1043v5 at the moment to test, but i have a ubiquiti-unifi-ac-lr also note, ubiquiti-unifi-ac-mesh is no separate device but an alias, as far as i know.

The list does contain every device or alias we'd possibly intend to migrate to ath79. That I added aliases as well just helps to see which aliases must not be forgotten at first glance. And gives ideas like "didnt these x revisions of that device all have the same hardware".

"Wants to test" is a mere reference, someone has ever announced interest in supporting the migration process for that particular device. The list is not endless; when you have time to do a migration on your own that's great. And when there's someone that "just" owns a device and would like to help I think that's worth a lot as well.

I currently have a break after my exams, so whoever has a device listed in "todo" above and cannot do the migration on his own, I'm happy to assist. That might not be enough in all cases, but should be sufficient for first time contributors like @heis2201.

And if you have no time to prepare the PRs, get me a list of a few devices you'd like to "just test" and I'll build the images for you as well.

[heis2201]

OK, I'm happy doing some testing over the next few days. Where can I see a list of test cases? Has anyone assembled a guide or at least recommends an order of doing things. Haven't spend any time thinking about it, but right now I would say, I test the migration from ar71xx to ath79 using sysupgrade, and in a second test I flash the OEM image and then flash the ath79 factory image. More or less correct?

[AiyionPrime]

The list you are looking for would be https://github.com/freifunk-gluon/gluon/wiki/Device-Integration-checklist .

The order depends on whether you've got stock or ar71xx firmware on your device. But looking at the list, you'll figure that out.

Have you built gluon before? And looking at recently closed PRs, do you want to do the PR on your own?

[heis2201]

I have never built gluon myself. How hard is that - where do I find documentation and requirements about it? is there some build infrastructure I could use, or do I build this locally?

I am happy to do the PR on my own.

[AiyionPrime]

https://gluon.readthedocs.io/en/latest/user/getting_started.html#building-the-images

That's a good point to start from. You'd build it locally, building gluon from scratch costs me about an hour on my 2013 laptop. Rebuilding is faster.

Then good luck with it :)

[heis2201]

Where would I find the container that is mentioned in the docs? Otherwise I would have to spin up and update a Debian VM first, which would take much longer.

Also, what the the RELEASE? v2021.1.1? Next, what would be my site configuration? The one from my regional freifunk community?

This thing is a bit bigger than I was hoping for.

Should I stop my support questons here, and we continue the conversation elsewhere (freifunk forum for example)?

[AiyionPrime]

If you want I'm available in hackint#gluon. You could join via webchat, that should be the fastest way.

https://webirc.hackint.org/#irc://irc.hackint.org/#gluon

We do support matrix as well: https://matrix.to/#/#gluon:hackint.org

[heis2201]

I have an IRC client and a matrix account, but I am afraid this would be something I would do late night, and rather spontaneous. But will see, once I get to it, I will be in touch

[udoschneider]

I can offer to test a ubiquiti-unifi-ac-mesh-pro. Will be this WE earliest though.

[heis2201]

sagt mal das target lautet ath79-generic oder ath79-nand ?

[AiyionPrime]

Kommt auf das Gerät an. Die erste Spalte der Tabelle gibt an, in welchem der beiden Subtargets das Gerät in ar71xx war.

[AiyionPrime]

Die Geräte, die du erarbeiten wolltest, scheinen generic zu sein.

[AiyionPrime]

The "ubiquiti-unifi-ac-lite-mesh" is not thing. Goal is 118 now.

[AiyionPrime]

I can offer to test a ubiquiti-unifi-ac-mesh-pro. Will be this WE earliest though.

@udoschneider earlier in this thread

Looking at recently closed PRs, you might find enough inspiration to do the PR on your own. Let me know, if you'd like to avoid building gluon yourself and would rather "just" flash and test the device; in which case I'd offer to provide the PR for you.

[udoschneider]

Looking at recently closed PRs, you might find enough inspiration to do the PR on your own. Let me know, if you'd like to avoid building gluon yourself and would rather "just" flash and test the device; in which case I'd offer to provide the PR for you.

If you have a ready to flash firmware I'd happy to try this now. I'm able to build gluon using the ffmuc site but don't understand the build process enough to guarantee I'm building the correct branch.

[AiyionPrime]

I will notify you when it's built. ETA 35m.

[AiyionPrime]

@udoschneider https://github.com/freifunk-gluon/gluon/pull/2462

[AiyionPrime]

Gestern Abend war das zweite Entwickler-Meeting diesen Jahres.

In Anlehnung an das Gespräch ergeben sich in der Liste oben zwei Änderungen. Zum einen wurde mir der Unterschied zwischen dem Target tiny und der Device-Class tiny aufgezeigt. Mein Ziel war es, das ar71xx-Tiny-Target in diesem PR nicht zu berücksichtigen. Die fehlenden Geräte habe ich den Listen oben hinzugefügt. Desweiteren haben wir einen besonderen Fokus auf Geräte beschlossen, die laut Multi-Meshviewer mehr als hundert mal betrieben werden. Diese Geräte von besonderer Dringlichkeit sollten leichter aufzutreiben sein und mehr Sinn stiften, als der Rest und sind obig dick markiert. Vielen Dank allerseits.

[AiyionPrime]

@rotanid closed the related PRs already, in todays Developer Meetup we agreed to dismiss the migration of xx/32 devices. That's not all of device-class tiny, but a significant ease on this issue.

That's not meant to be understood as "we don't want Gluon to support them", but merely none of of us is currently willing to put the necessary effort into these devices to get them running on a recent kernel again.

@NeoRaider suggested, someone willing could test an ath79-tiny approach. But that's not my intention to track here, as long as no one stepped up to get them working again.

[sheilbronn]

@rotanid closed the related PRs already, in todays Developer Meetup we agreed to dismiss the migration of xx/32 devices. That's not all of device-class tiny, but a significant ease on this issue.

That's not meant to be understood as "we don't want Gluon to support them", but merely none of of us is currently willing to put the necessary effort into these devices to get them running on a recent kernel again.

@NeoRaider suggested, someone willing could test an ath79-tiny approach. But that's not my intention to track here, as long as no one stepped up to get them working again.

Hello @rotanid and @NeoRaider, Just to be sure about some specific 8/32 devices, since I have several TL-WR710N v1.2 and v2.1 running Freifunk München and other community images. You are saying these WR710N's won't have a future, unless somebody will develop an ath79-tiny approach, even though they support OpenWrt 21.02.3 ? Is somebody aware of any work having started on this approach? Thanks very much!

[rotanid]

Hello @rotanid and @NeoRaider, Just to be sure about some specific 8/32 devices, since I have several TL-WR710N v1.2 and v2.1 running Freifunk München and other community images. You are saying these WR710N's won't have a future, unless somebody will develop an ath79-tiny approach, even though they support OpenWrt 21.02.3 ?

Yes, like every device with less than 64M memory. we tested many things and didn't achieve a usable image.

as a sidenote, OpenWrt 21.02 is not relevant as Gluon v2022.1 will be based on OpenWrt 22.03.

Is somebody aware of any work having started on this approach?

no to my knowledge

[blocktrron]

You are saying these WR710N's won't have a future, unless somebody will develop an ath79-tiny approach, even though they support OpenWrt 21.02.3 ?

What is Important to note here (As it is missing) is the fact a -tiny approach would only delay the inevitable by ~1 year. Thus nobody at the developer meetups was interested in such a non-longterm solution.