-
Notifications
You must be signed in to change notification settings - Fork 4
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
Fix unsatisfied dependencies by static Kconfig elements #223
Conversation
This file contains 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
Rename all old identifier `rpi_pico_w` to the new `rpi_pico/rp2040/w`, introduced with the new hardware model v2. Signed-off-by: Stephan Linz <[email protected]>
Add more details to the two different revision 1 and 2.1, e.g. new pictures of the different chips on PCB-A or different sessions for the `helloshell`sample. Signed-off-by: Stephan Linz <[email protected]>
Remove all the static default configuration in board extensions or snippets and introduce the more sensitive `Kconfig.defconfig` pattern for the RaspberryPi Pico and Pico W board extension. Signed-off-by: Stephan Linz <[email protected]>
Remove all the static default configuration in snippets and introduce the more sensitive `Kconfig.defconfig` pattern for the Seeeduino XIAO board extension. Signed-off-by: Stephan Linz <[email protected]>
Remove all the static default configuration in snippets and introduce the more sensitive `Kconfig.defconfig` pattern for the new STMicroelectronics Nucleo F767ZI board extension. Signed-off-by: Stephan Linz <[email protected]>
Remove all the static default configuration in board extensions or snippets and introduce the more sensitive `Kconfig.defconfig` pattern for the NXP MIMXRT1010-EVK board extension. Signed-off-by: Stephan Linz <[email protected]>
Remove all the static default configuration in board extensions or snippets and introduce the more sensitive `Kconfig.defconfig` pattern for the NXP MIMXRT1060-EVK board extension. Signed-off-by: Stephan Linz <[email protected]>
Add details about the new nix flake support. Signed-off-by: Stephan Linz <[email protected]>
Add details about the new sensitive Kconfig hoockups in boards extensions folder. Signed-off-by: Stephan Linz <[email protected]>
You can find the documentation preview for this PR at this link. It will be updated about 10 minutes after the documentation build succeeds. Note: This comment is automatically posted by the Documentation Publishing GitHub Action. |
tobiaskaestner
approved these changes
May 13, 2024
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.
LGTM
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
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.
With the new
Kconfig.defconfig
hookup in the Bridle board extension folder, all static configurations can be removed and Kconfig can work more sensitively, e.g. only influence the log level in the USB subsystem if the USB stack is really activated.This resolves #222