@borromini
I can live with the leds as is. Your call, if you want to implement dts changes.
Proposed RE220v1 .dts file
rename re200-v3 dts content to re220-v1 then prepend the = re200.dtsi content
then update led definitions per earlier post
I'm hesitant to change green:power as it might leave all leds off. I see led_power is referenced in a few aliases, so not sure ramifications of changing it.
In fact if night-mode is implemented in hardware, maybe it is why all lights are off during the U-boot failsafe phase.
I have been keeping an eye on this thread with a lot of interest. I have a RE220 v1 and would like to jump over to using openwrt instead of stock tp-link fw.
Some questions if I may:
1 - Would using the GPL link on TP-Link's website help? It is an openwrt version: https://static.tp-link.com/resources/gpl/re220v1_gplcode.tar.bz2
2 - Do you need another tester? I am happy to help test this out, building is beyond my skills right now.
3 - For more experienced builders/users - How long does it normally take from working model to being listed in the openwrt supported hardware tables?
I apologize in advance for the noob questions. Thanks.
Good stuff. I don't think it is needed at this point.
It would be great to have someone else test the RE220-v1
I'll repeat my comment from the other RE220-V1 thread.
Like other devices in this family (RE220v2, RE200) the 5GHz radio is not perfect. If you are happy with stock firmware, you may want to stick with it.
If you are relying on the device, you may not want to use it for testing.
@jedboy, I can prepare a build that works, but compilation will build the kernel modules in. I don't think it's the way to go; I'm not sure PR will be accepted in that case. Do you want me to try anyways?
I was able to flash my RE220 to the linked fw, but I had to downgrade to v.190616 because with more recent fw version from TP-link would produce an error about invalid fw.
Overall, I was able to get RE220 to work, however the lights would not light up but that is not a big issue for me.
Since this is a test device for me, I made several different configurations and everything was working as far as I could tell.
Then I ran into trouble. I decided to attempt to upload the same openwork firmware and things were going along nicely until I had a power outage. Sooooo... now I have a pretty white brick.
I am going to try to revive it so I am getting that together.
GPIO 44 does not map to a specific LED. I guess the correct thing is to remove it. I will test your updated image and see if removing it causes any problems (like keeping all lights off by default).
Alright, master images (including LuCI) can be found here, the patch to add support (which applies cleanly to 22.03 HEAD btw, in case anyone wants to try) is there as well. I am getting the message on 22.03 that the images are too big to be built though, but that might be some personal settings that are lingering. I haven't been able to clean them out though, so YMMV.