Hey guys, let’s retweet that message!
1 Like
@sinovoip @sinovoip1 any statement regarding current situation is very appreciated.
Thanks in advance
Please try openwrt i linked in the PR
The trace is fixed and timeouts are also avoided…seems to work with current firmware.only the sw bridge issue is there,but i guess @dangowrt can add a fw-check to disable bridge offloading.
New firmware will take some weeks to be released.
3 Likes
I’ve already reported the issues with Maxilinear v1.0.78 to Banana Pi’s technical team through the distributor I bought it from on a Chinese e-commerce platform.
I hope they also see this post. 
I am not sure I understood your post correctly. Are you having issues with the 1.0.78 firmware? Do you already have it?
I don’t have v1.0.78. I meant that I reported we need v1.0.78.
1 Like
Bump, we need this firmware
1 Like
Quick question — am I reading this right? @dangowrt just opened PR #23477 in OpenWrt (“generic: update MxL862xx DSA switch driver kernel”, May 21), and his kernel patch series for the MxL862xx DSA driver is already at v12 on LKML. To me that looks like the driver side really is being prepared for integration now.
Can anyone closer to the development confirm — is this what it looks like, or am I being too optimistic?
well only daniel can give you any timeline… and i believe there is no timeline according to the speed of changes i have been seeing from the patches he is upstreaming 1.0.70-1.0.73-1.0.75-1.0.78-1.0.80 and now 1.0.84 also, this one Netdev + BPF - Patchwork
1 Like
Can someone tell me what software bug exists in version V1.0.70 of the mxl862?
I checked relevant forums, and it seems the network port problem is caused by incompatibility with the open-source OpenWrt image.
If you can provide more detailed information, please let me know.
Mainline driver (used also in openwrt) sometimes run in timeout (internal phys not recognized or bot completely configured) because switch is initialized first completely with all possible options in non-dsa mode which has also some security relevant issues and then driver configures some parts for dsa. For upstreaming switch has to be initialized in very basic mode (full isolation,no web-ui,etc.) and then configured like dt says. With current software afair 10g port mode cannot be changed, 10gbase-r is imho fixed for ports used for cpu and sfp/phy.
1 Like
@sinovoip @sinovoip1 any words on this? Can we get some clarity on how you plan to handle this?
We would love some clear feedback on the topic.
Good morning @Pedro Ameruoso, they’re not going to answer you, and we don’t expect them to.
We’re still waiting for them to mass-produce all of this:
and this: BPI-R4 Accessories : WIFI7 module extension suites
You can wait a long time for them to show up and give any explanation; they’re only interested in the dollars.
Have a good day.
Equipment used: R4Pro 8X, CAT7 Ethernet cable, and a PC with a 10G Ethernet port.
Image name: BPI-R4Pro-8X-BE14-MT76-OpenWRT24.10-DSA-snand-251229.bin
MXL firmware version: 1.0.70.70
I tested the network port using the image from the BPI official website and did not experience any instability. Please try using the BPI official website image or source code.If you are using third-party source code, you may need to check the code’s compatibility.
I know that the downstream driver works,but mainline driver has some requirements which are not filled there. These require port isolation and very basic preconfig till driver kicks in. And then configuring all needed based on dts.
1 Like