[BPI-R4] TODO List

There is a catch, when controlling output pinsā€¦

GPIO control through libgpiod using the command gpiocli - Banana Pi Router design - banana pi single board computer open source project official forum BPI team (banana-pi.org)

Something else seems could be added to TODO list:

ebpf xdp support

DS-Lite, 6RD, MAP-E/T and 464xlat hardware offload support

1 Like

FYI i started new attampt to getting RSS/LRO to work based on upported patch from @balika011 with mtk. Btw. This is listed twice in the listā€¦and thought that ppe was working with 4g too,am i wrong?

1 Like

4g means 4gbps? If so seems correct.

I meant 4gb ram 36bit adressing afair was fixed for ppe too

wed; Re: [PATCH net-next] net: ethernet: mtk_wed: add support for devices with more than 4GB of dram - Daniel Golle

eth: [net-next,v3,4/4] net: ethernet: mtk_eth_soc: support 36-bit DMA addressing on MT7988 - Patchwork

1 Like

Yes there were some patches for this problem,but afaik ppe was independ of wed and ethernet fixes.

Could be this one,but not sure

https://patchwork.kernel.org/project/linux-mediatek/patch/97e90925368b405f0974b9b15f1b7377c4a329ad.1706113251.git.daniel@makrotopia.org/

PPE only supports 32bits address mode and hnat driver will allocate coherent memory for HNAT table , so we set dma mask to 32bits in ethernet driver to support 4GB dram.

1 Like

@frank-w do you have any details of the current status of the LRO / RSS patches (what works / what doesnt work ect) and where to find the latest version of the patches

I have worked on porting functionality from vendor kernels to newer ones so am very happy to assist on these patches if it would help.

I should have my bpi-r4 device just before the end of the year.

currently i talk to mtk about rss (not yet lro). they give me a patchā€¦but there are still some issues found (e.g. threaded napi)

And btw. I cleaned forum last 2 days from massive spammers. Also time not going into other tasks.

But pinctrl and and a bunch of dts patches are on the way to go into mainline linux.

1 Like

Ahh ok, is the RSS only patch available somewhere to review ?

But pinctrl and and a bunch of dts patches are on the way to go into mainline linux.

Nice ill keep an eye out for those changes

Sorry to bother, but since you have method to get touch with mtk, can you help to contact mtk about @ericwoud 's QinQ patch?

Imho we should focus on specific topics, and so stabilize ethernet driver while getting rss/lro working first (these issues are showing more often when throughput increases). Then other topics in networking. They also need to port their 5.4 patches to 6.6 and helping getting the tx timeouts fixed.

Once these tasks are done we can ask about additional parts. There are not much network people reachable thereā€¦only had second topic with pmic voltages discussed with them simultanously.

1 Like

Looks like the RSS patches have been published for 6.6

https://git01.mediatek.com/plugins/gitiles/openwrt/feeds/mtk-openwrt-feeds/+/445f9a3b0efbb0edf266b574a9d50693b8f906eb

1 Like

yes, after i got it working on mainline linux (6.13) :slight_smile: they added the patch to the sdk. daniel tries to add it to mainline openwrt

then we could look how to upstream it to net-next (but we have to make sure no other device gets broken by the changes, e.g. the additional irqs)

1 Like

Iā€™ll grab your 6.13 updates and give it a whirl :slight_smile: Iā€™m on 6.9.0 right now.

Imho 6.12-main would make more sense as it is lts kernel.

I built 6.13 just to try. Unfortunately it seems to be slower so Iā€™m gonna try 6.12

What exactly is slower? System itself,network,ā€¦? How do you test this?

Sorry for not being more specific - wireless network performance had dropped significantly. I havenā€™t tried 6.12 yet though, I just started building that now I was using 6.9-main from your tree for a baseline and was typically seeing around 300-400Mbps bidirectional thruput to a wired system (tested via iperf3 and the ookla speedtest.net cli test). The system was in the same physical location as well so as to rule that out. I tried a few different things to see if it was just the WiFi system weā€™re using but that doesnā€™t appear to be it. Iā€™ll report back as soon as Iā€™m done testing 6.12