[pmp] Use top-level straps for PMP reset values #2147
Conversation
Razer6
force-pushed
the
pmp-reset-straps
branch
3 times, most recently
from
7d6d3a1
to
392f556
Compare
By using top-level straps for the PMP reset configuration its easier to implement different reset configurations if there are multiple Ibex cores in the system. Signed-off-by: Robert Schilling <rschilling@rivosinc.com>
There was a problem hiding this comment.
This looks like a sensible change to me.
@GregAC can you see any problem with this? If not, I'm happy to take it.
|
I had intentionally avoid doing this with parameters when I first wrote it to avoid adding yet more parameters to Ibex, though given we've already got loads perhaps it doesn't matter. Ultimately this is probably what we have to do but I'll have a think about alternative methods. |
|
@Razer6 we intend to take this, I just need to do a couple of checks to ensure there's no issues for non PMP configs or breakages in other things we don't check in CI I hope to get this done over the next couple of days. |
|
@GregAC No hurry on that one. We have changed that in our environment and are not dependent on vendoring in a new version of ibex at the moment. |
By using top-level straps for the PMP reset configuration its easier to implement different reset configurations if there are multiple Ibex cores in the system.