Skip to content

Conversation

@graynode
Copy link

No description provided.

@xoviat
Copy link
Contributor

xoviat commented Nov 20, 2025

You're right, I went back and looked at the other files, and they are like this.

@embassy-ci
Copy link

embassy-ci bot commented Nov 21, 2025

@embassy-ci
Copy link

embassy-ci bot commented Nov 21, 2025

@embassy-ci
Copy link

embassy-ci bot commented Nov 22, 2025

@embassy-ci
Copy link

embassy-ci bot commented Nov 22, 2025

@embassy-ci
Copy link

embassy-ci bot commented Nov 25, 2025

@embassy-ci
Copy link

embassy-ci bot commented Nov 28, 2025

@embassy-ci
Copy link

embassy-ci bot commented Nov 28, 2025

("TIM", &["BRK", "UP", "TRG", "COM", "CC"]),
(
"TIM",
&["BRK_TERR_IERR", "BRK", "UP", "TRG", "TRG_COM_DIR_IDX", "COM", "CC"],
Copy link
Member

Choose a reason for hiding this comment

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

BRK_TERR_IERR, TRG_COM_DIR_IDX don't look like signal names. They're most likely a combination of multiple signals, where the signals are actually BRK, TERR, IERR, etc.

No idea what these are (TERR, IERR, DIR, IDX). Maybe they're something new in U3? If so we should ideally make it so they only appear in the U3 generated JSONs and not other families.

If you want to just those signals for now that's fine too, they can be added later when someone needs them.

Copy link
Author

Choose a reason for hiding this comment

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

You're correct about them being a combination of signals. They are identical to the U5. Should I rename the interrupt name similar to how other typos are fixed in the process function?

Copy link
Author

Choose a reason for hiding this comment

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

@Dirbaio I backed out that original code and now rename the divergent interrupt names. Let me know if this should be generalized or if this targeted rename is fine.

Copy link
Member

@Dirbaio Dirbaio Dec 2, 2025

Choose a reason for hiding this comment

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

nice!!

Yeah the rename is fine, the codebase is already full of similar renames 😅

@embassy-ci
Copy link

embassy-ci bot commented Nov 29, 2025

@embassy-ci
Copy link

embassy-ci bot commented Dec 1, 2025

@embassy-ci
Copy link

embassy-ci bot commented Dec 2, 2025

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.

3 participants