6 ms·
Both the "Rockchip engineers found that the Gregorian calendar contained flaws" in the title, and the "in A.D. 2013 Rockchip hardware engineers found that the n
by sampo 5y ago
Both the "Rockchip engineers found that the Gregorian calendar contained flaws" in the title, and the "in A.D. 2013 Rockchip hardware engineers found that the new Gregorian calendar still contained flaws, and that the month of November should be counted up to 31 days instead" in the post are sarcasm.
Apparently the Rockchip chip has a bug, where November has 31 days. And you need to have this workaround in software.
- zdw 5y agoOP here. It took me a while to edit down the original author's wit into something that would fit in the HN title box. Apologies to those who this confused - IMO that humor was one of the best features of the commit message. It feels somewhat unfortunate that the post title has been changed and is now just bland and boring.
- anticristi 5y agoI don't get why the RTC doesn't use seconds since some epoch. Encoding calendar in hardware/firmware feels wrong. Somewhat on a tangent, why don't we use TAI in hardware, since UTC is discontinuous?
- russdill 5y agoProbably has to do with hardware and firmware roots. Building an RTC that is programmable with year, month, day, hour, minute, second without multiplication and division is much much easier if you store the date time in year, month, day, hour, minute, second. You just need some simple comparisons whenever there is a rollover.
- wiml 5y agoApparently the comparisons aren't simple enough that people get them right, though.