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
DMI bridge integration #1657
base: main
Are you sure you want to change the base?
DMI bridge integration #1657
Conversation
Needs ucb-bar/chipyard#1619 |
Confirmed to boot Linux (albeit very very slowly). |
Ping @sagark @jerryz123 |
/** | ||
* Class which parameterizes the DMIBridge | ||
* | ||
* memoryRegionNameOpt, if unset, indicates that firesim-fesvr should not attempt to write a payload into DRAM through the loadmem unit. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps add a comment here that DMI+LoadMem is unsupported currently?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks good to me... but I'm not familiar with the bridge APIs enough to judge.
How does this deal with situations when both a TSIBridge and DMIBridge are built?
This adds a DMI bridge and associated collateral. Currently, it doesn't batch DMI requests nor does it support loadmem.
Related PRs / Issues
UI / API Impact
Verilog / AGFI Compatibility
Contributor Checklist
changelog:<topic>
label?ci:fpga-deploy
label?Please Backport
label?Reviewer Checklist (only modified by reviewer)
Note: to run CI on PRs from forks, comment
@Mergifyio copy main
and manage the change from the new PR.changelog:<topic>
label?