board/native: adapted Makefile.dep for netif init#3162
board/native: adapted Makefile.dep for netif init#3162miri64 merged 3 commits intoRIOT-OS:masterfrom
Conversation
|
Is this only needed for native, or are the other boards elided for a different reason? |
|
Actually, I have not looked at other boards (as the |
8a8c1d5 to
389c687
Compare
|
I updated it again slightly (and accidentally squashed already), now the Makefile has the identical structure of the |
|
Can't make line comments on mobile it seems so I have to comment here: Maybe out of scope of this PR, but I'm still opposed to using |
|
I actually agree, but I would like to continue this discussion somewhere else and merge this PR ASAP which then enables the merging of the |
|
Yes, ACK |
389c687 to
dc42b5c
Compare
|
ups, there was a still a bug in |
|
Re-ACK |
|
Now we have we see the fruits of using |
dc42b5c to
ae25d12
Compare
The new network stack does not now the concept of the defaulttransceiver, so this fix makes auto_init_ng_netif work for now.
|
To circumvent the problem above, I introduced a new pseudo-module called |
There was a problem hiding this comment.
Ah, got it… a relic from when netdev was super complicated :D
There was a problem hiding this comment.
you should know this... I just copied it from the Makefile.deps of the iot-lab and the samr21...
|
ACK |
|
&go |
board/native: adapted Makefile.dep for netif init
This application was not adapted to RIOT-OS/RIOT#3162 and RIOT-OS/RIOT#3188
This application was not adapted to RIOT-OS#3162 and RIOT-OS#3188
The new network stack does not now the concept of the defaulttransceiver, so this fix makes auto_init_ng_netif work for now.