-
Notifications
You must be signed in to change notification settings - Fork 512
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Outdated XDMA drivers #491
Comments
Hello, thanks for bringing this up. I'll sync up with the team and Xilinx on updating the DMA drivers. |
Hi, thanks for the quick response. Whilst you're doing that, can I please draw Xilinx/dma_ip_drivers#49 to the attention of you and Xilinx? Especially my comment (Xilinx/dma_ip_drivers#49 (comment)) which provides what should be a more amenable patch (minus the BEGIN/END comments to denote local changes in our vendored copy) than the existing one that is currently sitting there in review. Having fixed the timeout issue I then ran into this today, and reading the current sources in aws-fpga it's a long-standing bug that's still present as far back as those. |
Yes, it did, thank you (I replied to Karen at Xilinx/dma_ip_drivers#49 (comment)). |
We'll include the updates from Xilinx in our next releases. Closing this issue |
The official Xilinx XDMA drivers have seen recent updates, both for compatibility with "newer" kernel versions (even those old enough to be in Ubuntu 18.04) and highly important bug fixes. In particular, Xilinx/dma_ip_drivers@d1f334b meant that, if the CL was too slow at serving the DMA engine's requests (but still orders of magnitude below the timeouts), the XDMA driver would sleep for 10s and then report a timeout, despite the request actually completing. Our CL was slow enough that this happened under contention. Please update to this latest version; adding the AWS F1 PCI IDs to the table is all that's required for them to work.
The text was updated successfully, but these errors were encountered: