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.
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.
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).
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?
Hello everyone! Please help. I’ve been trying to build a firmware for the P4-Pro all night, but it’s not working. The firmware uploads, but the preloader is pointing to the wrong location. Does anyone have a ready-made firmware in the standard OpenVRT repositories? I just need certain packages that aren’t in the built-in firmware repositories.
Hi, are you talkong about BPI-R4 Pro? Why do you think preloader (TF-A or bootrom) is pointing to the wrong position? Do you see any output on debug uart?
I see that “bootconf_emmc=mt7988a-bananapi-bpi-r4-pro-8x-emmc” in uboot console, but if there is this var, i have error “Waiting for root device /dev/fit0”.
If i use
“setenv bootconf_emmc mt7988a-bananapi-bpi-r4-pro-emmc
run boot_production”
in uboot console, system is starting.
This problem only occurs when I build the image myself. Plus, after loading, half the interfaces stop working, and the router behaves erratically.
Sorry about my English))
Yes it is an issue i fixed in my tree already but not yet added to andrews PR
-boot_recovery=led $bootled_rec on ; run sdmmc_read_recovery && bootm $loadaddr#$bootconf#$bootconf_emmc ; led $bootled_rec off
+boot_recovery=led $bootled_rec on ; run sdmmc_read_recovery && bootm $loadaddr#$bootconf#$bootconf_sd ; led $bootled_rec off
To me, it looks this commit is not part of a branch. Is this correct?
Is there a branch I could try to get OpenWRT running on such a board that is as close to mainline / vanilla OpenWRT as possible, but working?