benpicco
benpicco
If we never do multicast address resolution in 6lo, couldn't `_resolve_addr()` be then simplified as ```patch --- a/sys/net/gnrc/network_layer/ipv6/nib/nib.c +++ b/sys/net/gnrc/network_layer/ipv6/nib/nib.c @@ -1374,9 +1374,12 @@ static bool _resolve_addr(const ipv6_addr_t *dst, gnrc_netif_t...
> if the neighbor is a router, it can be resolved with a router advertisement. but that's purely by accident, right? AFAIU there is nothing in the code that would...
What's the drawback of always setting `RADIO_SHORTS_ADDRESS_RSSISTART_Msk` to measure the real RSSI value?
Just some thought from my side: One goal of nanoCoAP sock was to use zero-copy network functions (`sock_udp_sendv()`, `sock_udp_recv_buf()`) to avoid having to keep a separate buffer around to copy...
> I'm happy to hand you an `iolist_t`. At some point, the iolist impl is going to copy your chunks into a larger buffer anway. Only if you need async...
It's certainly convenient, but my main use case was having a (small) buffer for the CoAP header and handing the payload over without coping it to a separate (CoAP header...
I did some digging to better understand the historical context on how we arrived at the current situation: Turns out both nanoCoAP (#5972) and GCoAP (#5598) arrived at roughly the...
This needs a rebase
Looks like this will need a rebase for `static-tests` to pass.
I don't quite understand the purpose if this. When you already have a SLIP connection, you might as well do CoAP over UDP. Sure, with this approach you can omit...