chrysn
Not right now, but I consider a few rewrites that might enable this. To justify adding code, it'd help if the docs could say a bit about how this is...
I like this because of previously unmentioned future possibilities: It paves the way to have documentation on features in a more parsable format than what is currently used for the...
RFC9177 has an extremely narrow scope and limitations, as outlined in section 3; in particular, it mostly performs well when the link on which it is used is understood well...
Thanks, that makes sense. Please let me know of your findings!
I don't know have the full picture of what a DECT stack looks like either. But there's quite a bit of it on top of the PHY (which the nRF91xx...
Coarse status update: Making progress on the interfaces, but they're still in flux a lot while I'm building initial applications to hammer out how they would eventually be used. As...
That doesn't seem to be related to multicast: CON requests inherently have a time after which one can be reasonably sure that no response will come, whereas NONs don't have...
A zero timeout will reap the request possibly even before it is sent out (and that won't get sent). There is no timeout because no time that we'd set by...
Having this checkable in F* is essential for checking embedded-cal – doing without provided methods would take away any API extensibility there.
Thanks for picking this up. We have a similar situation with the nrf52840dongle (which use the original nordic bootloader). Let's not slow down this effort over a generic solution, but...