-
Notifications
You must be signed in to change notification settings - Fork 13.7k
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
board specific driver and module organization #10964
Conversation
b9df0f3
to
5e2a09f
Compare
Not building yet |
aa1571c
to
3a2a234
Compare
Good to go. |
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.
I quickly went over this and it looks good.
# add_subdirectory(src/drivers/boards EXCLUDE_FROM_ALL) | ||
# | ||
# so include bbblue board specific code here: | ||
../src/init.c |
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.
Required?
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.
Probably not, but I didn't want to get too far into it without this board even compiling in CI.
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
With the new board directories we now have a place where board specific drivers and modules can reside.
These components are automatically included via standard cmake mechanisms in the board itself. It further simplifies the board configuration as well as the core Firmware source tree.