HammerBlade DMA #828
Open
HammerBlade DMA #828
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dpetrisko
force-pushed
the
zynqblade_dma
branch
from
630ba97 to
7e2e3ab
Compare
dpetrisko
force-pushed
the
zynqblade_dma
branch
from
7e2e3ab to
ee676e5
Compare
dpetrisko
force-pushed
the
zynqblade_dma
branch
from
ee676e5 to
66ccc82
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds support for DMA to the BlackParrot+Manycore Platform. This is a different mechanism than the backdoor simulation, which uses a DPI bridge to manually change the memory contents. In HammerBlade, we write to the V$ directly from BP, which means that we do not need to flush or invalidate the V$ as part of the DMA routines. Because of this, we add a configuration to select whether the DMA targets V$ or DRAM directly
Depends on #827 #826 #825