Skip to content
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

Clarify that DMI nop does not affect busy/error. #1055

Merged
merged 1 commit into from
Jul 16, 2024
Merged

Clarify that DMI nop does not affect busy/error. #1055

merged 1 commit into from
Jul 16, 2024

Conversation

rtwfroody
Copy link
Collaborator

The confusion was raised in the 2024-07-08 meeting.

The confusion was raised in the 2024-07-08 meeting.
@rtwfroody
Copy link
Collaborator Author

I considered changing "should" to "must" but does that then make it backwards incompatible? I really hope there are no implementations that have "nop" affect these status bits, though. It would break all kinds of things. So maybe should->must would be a bug fix?

Copy link
Collaborator

@pdonahue-ventana pdonahue-ventana left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What you have is good. I think that "must" is probably better but I worry about going through reviews, delaying ratification, etc. This isn't a "stop the presses" moment so I'm inclined to go with what's here.

@rtwfroody rtwfroody merged commit acaabf2 into main Jul 16, 2024
1 check passed
@rtwfroody rtwfroody deleted the jtag_nop branch July 16, 2024 16:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants