-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Updated chip config files from the library structs #1181
Conversation
(Some? All?) CI failures seem unrelated:
|
Need to check, likely to be unrelated to the content indeed... |
It's obviously a temporary bug in the respective GitHub Actions Build Environment - we should wait for it to be fixed before merging. |
It seems to be this issue (apparently an evergreen): actions/runner-images#675 |
@gszy The latest commit fixes the issue within the GH Actions workflow routine. |
a6cb2fd
to
c8fc656
Compare
In general, the chip config files should be kept in sync with the old library structs. Regenerate the files (using an ad hoc script) from the current library. The file name is generated from the chip description, all non-alphanumeric characters are replaced with underscores. It turns out some files have to have their names changed.
@Nightwalker-87, done. I think this commit, if merged, should be followed by a commit that would remove the old library struct completely. |
@gszy Thank you so much! 🥇 |
In general, the chip config files should be kept in sync with the old
library structs. Regenerate the files (using an ad hoc script) from the
current library.
The file name is generated from the chip description, all
non-alphanumeric characters are replaced with underscores. It turns out
some files have to have their names changed.
See #1180 (comment) and #1180 (comment).