Merged
Conversation
playfulFence
force-pushed
the
c61/uart
branch
2 times, most recently
from
166dd01 to
3947e6a
Compare
github-actions
bot
added
the
merge-conflict
|
New commits in main has made this PR unmergable. Please resolve the conflicts. |
github-actions
bot
removed
the
merge-conflict
MabezDev
approved these changes
Mar 26, 2026
Member
MabezDev
left a comment
MabezDev
left a comment
There was a problem hiding this comment.
The power of metadata, no code changes :D - ignoring the extra chip specific cfgs which we'll resolve later.
LGTM!
Member
Author
Yeah, it's really handy! When chip is as similar to some already existing ones as C61 is similar to C5, it mostly only comes down to updating the PACs, with all the metadata feature-gating we did, code does the rest for us automatically 😄 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
closes #5219
builds on top of / blocked on #5248
HIL survived 4 runs in a row, so probably success here 👍🏼
