Re: [riot-devel] Gnrc Router Solicitation Messages (Thomas C. Schmidt)

2017-10-30 Thread Thomas C. Schmidt
Hiho, to be more explicit: a Router Solicitation Messages should be sent out immediately after a link comes up. This usually happens by link triggers from the interface. Best, Thomas On 30/10/2017 14:27, smlng wrote: Hi Francisco, On 30. Oct 2017, at 14:21, Francisco Molina wrote: It's

Re: [riot-devel] Gnrc Router Solicitation Messages (Thomas C. Schmidt)

2017-10-30 Thread smlng
Hi Francisco, > On 30. Oct 2017, at 14:21, Francisco Molina wrote: > > It's not really that i wan't to change the interval. The thing is my node > goes into deep sleep and to be battery efficient I need Router Solicitation > Messages to go out as soon as it wakes up, which is not happening wit

Re: [riot-devel] Gnrc Router Solicitation Messages (Thomas C. Schmidt)

2017-10-30 Thread Francisco Molina
Hi, >why would you want to change the router solicitation interval >(RTR_SOLICITATION_INTERVAL) outside the scope foreseen by the RFC? It's not really that i wan't to change the interval. The thing is my node goes into deep sleep and to be battery efficient I need Router Solicitation Messages to

Re: [riot-devel] Need some orientation about using vendor SDK when porting MCU

2017-10-30 Thread Hauke Petersen
Hi Cristiano, I think in general, the inclusion of at least the vendor/firmware headers for those CPUs should probably be done in a similar fashion than the inclusion of the stellaris ware (cpu/stellaris_common). But dependent on the amount of headers (or even library source files), it would