-
Notifications
You must be signed in to change notification settings - Fork 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
tree-wide: Introduce netif feature and use it #20682
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.
Thanks for that! I haven't compared the removed list of boards vs. added FEATURES_PROVIDED
in detail, but I'd trust you to have done that thoroughly enough - in the end it is only relevant for apps/tests using the default board features.
Just a minor addition below.
Sounds good to me, I tested it with a dwm1001, an arduino nano 33 ble (and the sense one) and didn't notice any unexpected behavior on the default example. My only question is about the following line : RIOT/examples/default/Makefile Line 49 in 0641ab2
Since you added a feature it should be the same as this one I think :
|
This gets rid of a long list of boards with network interfaces and instead let's boards (or MCUs with peripheral network interfaces) provide the netif feature. The apps that before used the long list are not depending on the feature instead (in case of the default example, this is an optional dependency). Co-authored-by: mguetschow <mikolai.guetschow@tu-dresden.de> Co-authored-by: mewen.berthelot <mewen.berthelot@orange.com>
5264a06
to
97a6543
Compare
Indeed! Good catch :) |
The ESP32 Ethernet Kit has only a single GPIO pin exposed to SAUL via `saul_gpio`, but that GPIO doubles as PHY clock input when `esp32_eth` is used. Hence, the `saul_gpio` dep should be optional and only kick in when `esp32_eth` is not used.
Looks like the The second commit fixes that issue. |
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.
Good catch, thanks @maribu!
Contribution description
This gets rid of a long list of boards with network interfaces and instead let's boards (or MCUs with peripheral network interfaces) provide the netif feature.
The apps that before used the long list are not depending on the feature instead (in case of the default example, this is an optional dependency).
Testing procedure
Ideally, no change in binaries. There may be some boards that actually do have a network interface but were not listed in
Makefile.boards.netif
that now qualify as having a network interface, if the feature was provided on MCU level (only for peripheral netifs).Issues/PRs references
Partially fixes #20680