Dmitry
Dmitry
First three xdma_xfer_submit timeouts you see are probably because of too small timeout value (compared to transaction size, which is big as you mentioned) or because of #311. It's impossible...
Hi Prandr, this all sounds incredible. Looks like you brought XDMA to another level. I'll give it a try on my platforms and share my results here. By the way,...
Hi @vineetskumar , try again with community patch #240
@vineetskumar okay, these were worth trying. Error 512 is a timeout. Original XDMA code returns code 512 instead of ETIMEDOUT, so this makes some confusion. According to logs I see...
Hi @krithick14, try the following recommendations: 1. Set up ILA to watch XDMA AXI bus, and perform multiple transactions. 2. Your transfer rate depends on AXI frequency, so try to...
@zhaochengjie0405 solution #333 and explanation #332
Hi @jason77-wang, current code returns error 512 in case of timeout of r/w transaction and in case of blocking read of event device. This error code is undefined in userspace...
Hi @free43 , that's an interesting question. In my understanding, the driver in /drivers/dma/xilinx is a _driver for a SoC that has built-in hard IP from Xilinx_, that's why it...