haukepetersen commented on pull request #970:
URL: https://github.com/apache/mynewt-nimble/pull/970#issuecomment-846002384
ok, then its not just RIOT :-). Anyway, I still think a clean initialization
during startup would be best, also considering timing effects of the current
late
haukepetersen commented on pull request #970:
URL: https://github.com/apache/mynewt-nimble/pull/970#issuecomment-845746016
@andrzej-kaczmarek I was expecting this, though I was still hoping we could
simplify this part of the code a little bit by streamlining it... So do I get
it
haukepetersen commented on pull request #970:
URL: https://github.com/apache/mynewt-nimble/pull/970#issuecomment-839512979
@andrzej-kaczmarek any chance you got a minute to look at this?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on
haukepetersen commented on pull request #970:
URL: https://github.com/apache/mynewt-nimble/pull/970#issuecomment-820187387
Yes and no. Seeding the jrand48 during init of course takes away the
(non-deterministic) delay between TRNG init and jrand48 seeding. But if I
understand
haukepetersen commented on pull request #970:
URL: https://github.com/apache/mynewt-nimble/pull/970#issuecomment-819651896
Forgot to reference - here is the path towards the bug in RIOT:
https://github.com/RIOT-OS/RIOT/pull/16317
--
This is an automated message from the Apache Git
