Tx write only #135
Merged
Tx write only #135
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
This can save some resources in case reading the tx buffer is not needed. It also makes it easier for synthesis to infer BRAM, tested on Spartan6.
|
Applied, I just did some minor changes with ac4c2a7. |
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.
Allow liteeth txslots to be write only. Enable it in case the firmware does not need to read back the buffer. This can save a substantial amount of resources. Tested on Spartan6. Without it, txbuffers are implemented as distributed RAM, probably due to the 2 read ports. With this patch, it is implemented as BRAM.
Needs to be pulled in conjunction with the corresponding liteeth patch.