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 user with the knowledge of timer overflow. The latest example was a bunch of HPE SSDs that stop working after 32.768 hours (a little less than 4 years). Bad when you have several of them in a RAID for redundancy :-) https://www.techradar.com/news/hpe-ssd-drives-could-fail-at-this-critical-moment So I'd vote for the (small) additional overhead, even on 8-bit µCs due to safety reasons. Unless the implementation can produce the correct timer representation with, say, C-preprocessor magic at compile-time. Ralf -- Dr. Ralf Schlatterbeck Tel: +43/2243/26465-16 Open Source Consulting www: http://www.runtux.com Reichergasse 131, A-3411 Weidling email: off...@runtux.com _______________________________________________ devel mailing list devel@riot-os.org https://lists.riot-os.org/mailman/listinfo/devel
