-
Notifications
You must be signed in to change notification settings - Fork 972
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
Move CYW43-related PICO_CONFIG lines to cyw43_driver.h #2002
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry, I don't like this. Why are we putting Pico specific GPIO configuration in src/rp2_common/pico_cyw43_driver/include/pico/cyw43_driver.h?
I'm happy to take out the Pico-specific values from |
I don't really like these defines in cyw43_driver.h. I'd rather remove the PICO_CONFIG lines completely if they're causing a problem. Although this sounds like a tooling defect to me. |
2e8ae23
to
2499769
Compare
I've just force-pushed an updated commit, which removes the defines from |
ta |
- Re-synchronise the PICO_CMAKE_CONFIG: entries with the corresponding PICO_CONFIG: entries - Fix a silly typo I made in #2002 - Enhance config-extraction scripts to catch similar typos in future
- Re-synchronise the PICO_CMAKE_CONFIG: entries with the corresponding PICO_CONFIG: entries - Fix a silly typo I made in #2002 - Enhance config-extraction scripts to catch similar typos in future
- Re-synchronise the PICO_CMAKE_CONFIG: entries with the corresponding PICO_CONFIG: entries - Fix a silly typo I made in #2002 - Enhance config-extraction scripts to catch similar typos in future
This is a follow-up to #1982 - I'm afraid that I didn't think to check at the time, but the
tools/extract_configs.py
script was getting upset that there were duplicate PICO_CONFIG entries in different files. So this PR fixes that.