-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Revert "Remove MCU variable" - unbreaks esp8266 #20409
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
Conversation
The following symbols disappeared:
I have a hard time to figure out why. But honestly, let's not revert this. It exposed how fragile and weird things currently are. I'm working on a fix. |
Thanks Ben for spotting this, Marian for picking it up, & sorry you're getting the fall-out. I agree with Marian that we should better find what is really using MCU covertly here. That this went unnoticed shows how brittle relying on this kind of variables is, compared to using features that are (now about to be) rigorously checked and documented. (Then again, if we don't come up with something working, reverting is the next best option, to be followed by a deprecation and more thorough investigation).
MCU is just as illdefined, especially given its only documentation was inaccurate. CPU really just means "whatever is grouped in one directory |
Follow-up-for: RIOT-OS#20397 Closes: RIOT-OS#20409 Closes: RIOT-OS#20415
Closing in favor of #20415 |
Contribution description
This cleanup broke boot on esp8266, not sure if other things broke too.
I'm not convinced this 'cleanup' is even worthwhile since 'CPU' isn't an exact term either (could mean just the CPU core).
If you disagree, feel free to open an alternative PR that fixes the issue on a more fine grained level.
Testing procedure
Flash any application on e.g.
esp8266-esp-12x
- onmaster
it will output nothing currently.Issues/PRs references
reverts #20397