Hi,
There might also be some kind of `offset` setter for the `now()` return
value required, when considering that this new timer API should also be
backended by RTC and/or RTT. This can come in handy to set the system time
with time synchronization protocols like (S)NTP.
Cheers,
Martine
Hi,
I think that giving more precise APIs and removing the low level
implementation detail from it is a good thing.
It means that the library can adapt to the current hardware and PM
constraints.
I have questions regarding the transition to new timers.
As several modules have dependencies
Hej,
On 01/25/2018 01:29 AM, PyroPeter wrote:
Hi,
to make matters even more complicated:
Timers and PWM are the same thing on most platforms. It would be nice
if one could choose whether to use interrupts or PWM pins or both per
timer. (e.g. using both the interrupt and a PWM pin enables one
Hi,
to make matters even more complicated:
Timers and PWM are the same thing on most platforms. It would be nice
if one could choose whether to use interrupts or PWM pins or both per
timer. (e.g. using both the interrupt and a PWM pin enables one to
bitbang the protocol of WS2812 LEDs very
Hi all,
I guess it is time to coordinate improving RIOT's timers - again.
IMO xtimer is a dead end. It was designed with good intentions, but
unfortunately with not much real-world experience. It has also
(d)evolved into a complex and inflexible #ifdef-mess...
Here's what I think is bad about
