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

[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 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 with gnrc default 
set-up. That's why I was asking how I can trigger one in the cleanest way. 
Cheers,


Actually, you shouldn't need to trigger a RS explicitly. This should happen
automatically within RIOT, i.e., send an RS whenever a link gets ready, which
also applies to wake up from sleep. Hence, (IMHO) this needs to be fixed in
the network stack.

@miri64 might know the right place? Anyhow, if not already done: please open
an issue addressing and describing this issue, so we have it officially and
trackable.

Best,
   Sebastian
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel



--

Prof. Dr. Thomas C. Schmidt
° Hamburg University of Applied Sciences   Berliner Tor 7 °
° Dept. Informatik, Internet Technologies Group20099 Hamburg, Germany °
° http://www.haw-hamburg.de/inet   Fon: +49-40-42875-8452 °
° http://www.informatik.haw-hamburg.de/~schmidtFax: +49-40-42875-8409 °
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

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

[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 with gnrc 
> default set-up. That's why I was asking how I can trigger one in the cleanest 
> way. Cheers,

Actually, you shouldn't need to trigger a RS explicitly. This should happen 
automatically within RIOT, i.e., send an RS whenever a link gets ready, which 
also applies to wake up from sleep. Hence, (IMHO) this needs to be fixed in
the network stack. 

@miri64 might know the right place? Anyhow, if not already done: please open
an issue addressing and describing this issue, so we have it officially and
trackable.

Best,
  Sebastian
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

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

[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 go out as soon as it wakes up, which is not happening with gnrc
default set-up. That's why I was asking how I can trigger one in the
cleanest way. Cheers,

Francisco
___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel

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

[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 be definately worth a thought to consider adding the vendor 
libraries as packages. This way there would be no need for keeping all 
these files in the RIOT source tree directly, and code duplication would 
not be an issue. Further, it would be simple to update the libraries. 
Drawback here is, that we/someone would need to provide a public 
available repository containing these libraries - I guess TI is not 
doing this, right?


Cheers,
Hauke


On 28.10.2017 13:47, Cristiano Gavião wrote:

Hello Riot Devs,

As I have written before, I would like to use Riot in my 6lowPan 
project that is using CC1310 and CC1350 MCU.


No long ago, Texas Instruments have separated its common provided SDK 
into CC13XXWARE and CC26XXWARE. Currently there are many code that are 
still equals, but I did a file to file compare using Meld and found 
significant differences between some of them (9 files).


What I heard was that in the next MCUs versions (CC1312 and CC1352) 
more differences will come...


Besides that, those MCU have written in they ROM the most used SDK's 
driverlib binaries. So using the binaries instead flash them can give 
us more space for the applications.


So I would like to use headers and driverlib from CC13XXWARE in a best 
way that would fit in Riot and also facilitate maintenance when new 
updated come.


Would like to hear suggestion about what would be the best approach to 
work on this.


thanks for any comment,

Cristiano

___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel


___
devel mailing list
devel@riot-os.org
https://lists.riot-os.org/mailman/listinfo/devel