[BPI-R4-PRO] Mainline OpenWRT

I don’t think it will be merged this net-next cycle.

Have you tested my tree with now already the pcie patches added?

Hey guys. Do you have any estimates on when the official OpenWrt firmware might appear in the selector?

The R4Pro pull request is open,but seems stalled so far…i prepared some additional patches for discussion,but got no answer on it yet

1 Like

First of all, thank you for your contribution. I saw the open PR it’s been inactive for quite a while, which is why I wanted to ask.

it will stay inactive for lots of time IMHO. Lots of components are missing upstream… Dango mentioned in that pull request he prefers waiting for the maxime series to be complete. If there is no change into that than we will probably see proper support EOY 2026.

Yes,but the version from pr is not working and i got it working so far and added pcie overlays,8gb (waiting for my own pr) and also the mxl switch which can use the current driver from daniel not yet upstream.

Not talking about parts daniel wants to wait for upstream like the ethmux and aeonsemi phy.

1 Like

are we going to have the same issue as the non pro. where we need to patch for 8gb ram? or once its mainstream it will automatically detect?

Bl2 is same…either flash 4gb image and update bl2 or flash 8gb image if it exist

I’ll try to revisit it this week. I had two other devices land on my desk begging for support, and all the necessary drivers already exist for them, so they got priority.

1 Like

had sometime and based on Frank’s Opennwrt branch R4Pro got the aeonsemi mxl to work … the docs are wrong…looking now at the sfp’s / 10g (wan/sfp) but no luck yet

You need aeonsemi downstream driver + dts +firmware to be recognized and to work the ethmux patches for mtk eth driver and mxl driver + dts change

Edit sorry i thought you did not got it working…seems you added driver for the phy from latest mtk feed with this strange bbu api (and debug) code. The wan is basicly same only needs patch for mtk driver and dts for the mux. That part was a bit strange and i had modified in my repo due to phylink hangs/traces…maybe look in my kernel repo how i added mux there

Btw. My latest state with different mxl driver is this

But misses fit definition for nand. And needs to be rebased on latest mxl patches and andrews PR (but still modifies existing patches for adding dts to makefile).

1 Like

Hey guys what screw do I need to use this ssd? How can I move the standoff without damaging the board? Maybe its better to get just another standoff then I can use the M.2 screw? Do we have dimensions of the possible standoff screw? Or better to buy a 2230 to 2280 adapter?

https://www.amazon.com/Mounting-Screws-Gigabyte-ASRock-Motherboards/dp/B08ZD81HDR/ref=sr_1_5

1 Like

this one the screws heads are to slim. I found something similar on amazon.de but the hole is big and the head should not be too tall. I don’t see any groves in the motherboard. 633 Stück Laptop Schrauben, M.2 NVMe SSD Montage Schrauben Set, M2 M2.5 M3 Notebook Computer Schraubenset mit Schraubendreher für Asus Gigabyte MSI-Motherboards, Kompatibel mit IBM/HP/Dell/Samsung : Amazon.de: Computer & Zubehör

It seems like the simplest and fastest solution. You could also 3D print it—maybe one of your friends has a 3D printer.