<mrnuke>
Ansuel, robimarko: Have you seen those dumb cache flush ops in edma-v2 (qca-nss-dp) ? Do you thiunk it would work if I used dma_alloc_coherent() for the DMA descriptors (not skb data)
goetz has quit [Quit: goetz]
philipp64 has left #openwrt-devel [#openwrt-devel]
<sandberm>
I stumbled on package/utils/yafut that fails a github job due to mismatch in PKG_MIRROR_HASH. While having CI check that fix, a few others came up. So my question really is that is there a maintainer tool to fix them all recursively or should I file this patch I prepared for yatuf?
<sandberm>
The fix was to run 'make package/utils/yafut/check FIXUP=1' so no work involved really.
JuliusBairaktaris has joined #openwrt-devel
<JuliusBairaktaris>
:jow Hey, my name is Julius Bairaktaris I am a Uni Student from Germany and i would like to offer my help to fix the spam detection problem. (https://github.com/squidowl/halloy/pull/189)
<JuliusBairaktaris>
*jow:
JuliusBairaktaris has quit [Read error: Connection reset by peer]
philipp64 has joined #openwrt-devel
<robimarko>
mrnuke: Sorry, just saw it now, they are seriously still using drop dropped ASM DMA OP-s?
<mrnuke>
Oh yeah! dmac_inv_range_no_dsb() sprinkled all over edma_{tx,rx}.c
<robimarko>
Yeah, those need to be converted to the generic APi
<robimarko>
Ansuel did the same for NSS-DRV, DMA is beyond me
<mrnuke>
What those cache flush ops do is, they make sure any writes are flushed out to the memory. So when an external device reads the memory, they get the data the CPU intended to be there
<mrnuke>
Otherwise said data could remain stuck in cache and never get to memory
<mrnuke>
I get the concept. It's the hadrware interface that I don't understand yet