benpicco
benpicco
Isn't the ZTimer RTT backed limited to 1ms accuracy since it only provides ms as a unit? And it requires a unit conversion each time the time is read /...
> * which RTT can actually do 64khz? I didn't come up with this format - it's what's used by [RFC 3971](https://www.rfc-editor.org/rfc/rfc3971.html#section-5.3.1) (and probably some others too). Most RTTs do...
Deep Sleep is without RAM retention, yes. The issue with `ztimer_msec` is that we lack an API that lets us expose multiple low-power timers, there can only be a single...
Yes or rather it becomes inherently racy to use the RTT alarm to wake from Deep Sleep as some random driver might set it's own RTT alarm inbetween.
The thing is that often you don't need to keep state at all, so reboot after Deep Sleep is the right thing to do.
My take on this is that it's a cleaner alternative to `rtt_rtc` that provides sub-second time-stamping. `rtt_rtc` stared as a compatibility layer for MCUs that lack a hardware RTC to...
What are ```C static inline uint64_t rtt64_sec(uint64_t sec); static inline uint64_t rtt64_usec(uint32_t usec); ``` supposed to do?
I'm fine with exporting the helper functions, but I would like to keep the convenience functions (and the `periph_rtt` aligned naming) in place.
> Any results yet? So far no improvements, but also no worse than master. (I tested `examples/benchmark_udp` and `for i in {10..20}; do echo $i | nc -u -6 -w0...
Uh so this turns out to fix a gnarly pktbuf corruption issue with SLIP