Skip to content

Avalon-MM: use BitVectors and remove unused field#187

Draft
JvWesterveld wants to merge 2 commits intoclash-lang:mainfrom
JvWesterveld:avalon-mm-changes
Draft

Avalon-MM: use BitVectors and remove unused field#187
JvWesterveld wants to merge 2 commits intoclash-lang:mainfrom
JvWesterveld:avalon-mm-changes

Conversation

@JvWesterveld
Copy link
Contributor

@JvWesterveld JvWesterveld commented Jan 11, 2026

Breaking changes.

Does anyone know what the unused field fixedWaitTime that's removed in the first commit was supposed to be used for?

Perhaps I should also change the irqList field type over to BitVector.

Which should be easier to work with (fever type coercions) than with the previous `Unsigned`.
@rowanG077
Copy link
Member

rowanG077 commented Jan 11, 2026

I didn't write it. But I expect fixedWaitTime is used to indicate the output needs to be asserted for that many cycles at least. See 3.3.2 Wait-States in https://www.cs.columbia.edu/~sedwards/classes/2008/4840/mnl_avalon_spec.pdf

@JvWesterveld
Copy link
Contributor Author

Right, it indeed looks like fixedWaitTime concerns the fixed wait-states for write transfers as documented in section 3.3.2.1. So the implementation made sure to only allow connecting managers and subordinates with the same value for this parameter, which makes sense to me now. I'll probably drop the commit.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants