Skip to content

sys/auto_init: added mechanism for initialization of network devices#2891

Merged
miri64 merged 7 commits intoRIOT-OS:masterfrom
haukepetersen:ng_autoinit_netif
May 1, 2015
Merged

sys/auto_init: added mechanism for initialization of network devices#2891
miri64 merged 7 commits intoRIOT-OS:masterfrom
haukepetersen:ng_autoinit_netif

Conversation

@haukepetersen
Copy link
Copy Markdown
Contributor

This PR introduces a mechanism, that allows for auto-configuration of network interfaces. The configuration is normally done by each board (of course it is interesting only for those that have network interfaces), but can be overwritten by the application (may you want a different MAC layer...).

@haukepetersen haukepetersen added Area: build system Area: Build system Type: new feature The issue requests / The PR implemements a new feature for RIOT Area: drivers Area: Device drivers NSTF labels Apr 29, 2015
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Either name this function and the module ng_auto_init_netif or just auto_init_netif. It's worse enough that ng_ has become an infix for MODULE_ macros and net_ doxygen groups. For the future switch-over I'd like to have as few corner-cases as possible. Currently there is (in sed syntax) \<ng_, \<NG_, \<MODULE_NG and \<net_ng.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

but this does syntactical not make sense: the notion is: auto_init_MODULE_NAME, and the module is called ng_netif...

@miri64
Copy link
Copy Markdown
Member

miri64 commented Apr 30, 2015

αpart from the comments above and the fact, that there is still room for optimization IMHO (as always) I'm fine with this PR.

@haukepetersen
Copy link
Copy Markdown
Contributor Author

addressed comments. Should I squash?

@miri64
Copy link
Copy Markdown
Member

miri64 commented Apr 30, 2015

Yes, please (This is an ACK, if travis is happy)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Priority needs to be adjusted

@miri64
Copy link
Copy Markdown
Member

miri64 commented Apr 30, 2015

Please address my last two comments also

@haukepetersen
Copy link
Copy Markdown
Contributor Author

squashed. Wontfix your last comments as in my opinion they do not hurt and changing the prio would not change anything...

@miri64
Copy link
Copy Markdown
Member

miri64 commented Apr 30, 2015

Alright then … re-ACK

miri64 added a commit that referenced this pull request May 1, 2015
sys/auto_init: added mechanism for initialization of network devices
@miri64 miri64 merged commit ec018b2 into RIOT-OS:master May 1, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Area: build system Area: Build system Area: drivers Area: Device drivers Area: network Area: Networking Type: new feature The issue requests / The PR implemements a new feature for RIOT

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants