Remove IPv6 link time dependency on an RF phy #2551
Conversation
|
/morph test |
|
@mbed-bot: TEST HOST_OSES=ALL |
Result: SUCCESSYour command has finished executing! Here's what you wrote!
Outputmbed Build Number: 719 All builds and test passed! |
|
[Build 842] |
|
Who should review this changeset? Please mention them here |
|
@kjbracey-arm @SeppoTakalo @juhhei01: you guys probably know something about this.. |
|
The MeshInterface change seems good to me. Do we think we can live without the MAC bit in the random? Is the mbed TLS support hookup definitely working? |
|
+1 |
|
@kjbracey-arm TLS support should be working, as client applications without an entropy source do not work. Turning on null entropy fixes this. Notes could be added to the example to turn on null entropy if the platform does not support it. Alternatively, an entropy source C++ API could be defined and the RF drivers could support it. This would take a bit longer to implement though. |
Create a Nanostack rf phy class to wrap various rf physical interfaces. Allow this phy to be set at runtime rather than compile time.
c1728p9
force-pushed
the
runtime_configuration
branch
from
bf10244 to
126c8be
Compare
|
@c1728p9 @kjbracey-arm @SeppoTakalo Anything blocking this from being merged? |
|
Will plan be part of mbed OS 5.2, not back ported to mbed OS 5.1 |
Create a Nanostack rf phy class to wrap various rf physical interfaces.
Allow this phy to be set at runtime rather than compile time.