I merged openwrt:master into openwrt mr53 branch the other day but I think the histories are a bit diverged. I'll clean it all up at some point.
I've installed one of them in my house after making a bracket (its a simple clip that is secured with the side M2.5 screw, and 2 plaster screws into the ceiling. printed in petg and hasn't fallen off yet). I'll put the .stl file in the repo when I get a chance.
Some observations
I'm struggling to get good wifi speed from this thing. Compared to a tp-link deco m5 running the same code base (there are patches in my repo for this)-
- deco is a IPQ4019 2x2 with basic internal antennas
- deco: I get consistent ~500Mbits/sec on my phone with 2x2 at 80MHz channel
- MR53: struggles to get to 250 in the same environment...

- both have essentially the same config- 5 SSIDs on both bands (10 total).
- looks like the MR53 rebooted/crashed last night- uptime only 19 hours and I definitely didn't reboot it.
so clearly not done just yet. Will have to make sure its not the ethernet- havent had a chance yet. Or it could be the wifi- looks like its falling back to generic board2.bin which doesn't seem right. Pretty sure the ART calibration is being pulled in correctly though.
EDIT: I'd added tftp put to the uboot, and before I blew everything away I grabbed the original ubi partition. From that I found the ath10K bin files for the mr53, and I made a matching board2.bin from these. This worked and I got a bit more excited seeing close to 400Mbps. I tried again this morning and the mr53 crashed/rebooted during the test...
Next I'll use the ath10k firmware blob instead of the ct one in openwrt and see if that makes a difference. For the system crash it might be power related but I've got it running about 20m from a PoE+ aruba switch so should be fine. I'll spin another one up on my bench and leave that running for a bit, with console attached in case the kernel spews something out before it dies.
EDIT2: Throughput limit is probably CPU hitting the ceiling- I will check that next time I can throw a client at it. Theres no NSS enabled on this build its all going through CPU. Iperf client on ethernet hits ~250Mbps max (single thread). With two threads (2xCPUs) we max both out and get up to ~500... The wifi<->ethernet path is probably similar overhead or worse, which aligns with the ordinary performance. So its OK but not as performant as my old tp-link setup, aside from better RF coverage.
