As far as I understand, the new timer implementation would not use 64
bit for the timer and the user is responsible for not overrunning the
timer? Note that I haven't looked a the implementation yet, so forgive
my ignorance.
Over the years my experience is that it's no good idea to burden the
Dear RIOTers,
As part of the first phase towards the integration of Kconfig in RIOT,
a tracking list has been created [1]. In that issue we want to keep
track of the progress of configuration exposure (to Kconfig) for the
different modules in RIOT. Currently most of the listed modules are the