Hey guys, If I install the current OpenWrt image from this page, will I be able to upgrade later to the official release using the system upgrade option in the UI?
as its based on openwrt, there should be no problem in doing so
Wow,yesterday it was still new,but got some missing reviews by andrew.
It is only the first step for ethmux (which is last step)…not sure if there is any code supporting ethmux based on it.
I don’t think there are any POCs… but yeah I am monitoring the maxlinear driver series from daniel too.
Yes,but there the upstreaming requires a new firmware that have to be created first (looks like by daniel) to have a clean state and then a very basic driver. Current firmware requires configuring all settings (like vlan,…) which will bloat first version of driver.
Got info from daniel that it basicly works,but without dsa tag needs patch for mtk driver. And there is no offloading for vlan/bridging yet so there will be performance issues.
But my kernel and my openwrt tree uses a full driver working with current firmware.
1 Like
Already in net-next so will probably be in 6.20 (kernel 7?). Will need to backport to 6.12 (or potentially 6.18).
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