-
Updated
Oct 27, 2020 - C++
hardware-acceleration
Here are 85 public repositories matching this topic...
-
Updated
Oct 28, 2020 - C++
-
Updated
Mar 30, 2020 - JavaScript
-
Updated
Aug 27, 2019 - C
-
Updated
Oct 15, 2020 - C
-
Updated
Jul 3, 2018 - C++
-
Updated
Oct 14, 2020 - C
-
Updated
Sep 29, 2020 - Java
-
Updated
Oct 4, 2020 - C++
-
Updated
Oct 26, 2020 - Python
-
Updated
Aug 7, 2020 - Shell
-
Updated
Jan 5, 2019 - VHDL
-
Updated
Oct 27, 2020 - Python
-
Updated
Dec 10, 2019 - Python
-
Updated
Jul 30, 2020 - TypeScript
-
Updated
Oct 22, 2020 - Verilog
-
Updated
Oct 27, 2020 - C
-
Updated
Oct 5, 2017
-
Updated
Jul 11, 2018 - Jupyter Notebook
-
Updated
Aug 22, 2020 - Python
-
Updated
Aug 23, 2020 - C++
-
Updated
May 2, 2017 - C
-
Updated
May 4, 2020 - Python
-
Updated
Oct 22, 2020 - C
-
Updated
Oct 26, 2020 - C++
-
Updated
May 4, 2020 - VHDL
-
Updated
Sep 1, 2020 - JavaScript
-
Updated
Oct 19, 2018 - C++
Improve this page
Add a description, image, and links to the hardware-acceleration topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the hardware-acceleration topic, visit your repo's landing page and select "manage topics."
Right now it is very easy to deadlock the whole system if a PE e.g. reads from the DDR and writes to the DDR but never deals with the result of either request. Right now such a situation is quite hard to debug. Most often this scenario happens when the DMA engine is active at the same time.
Right now I have to possible solutions: