3 ms·
As an aside dang would probably ban my account if I let rip about what I think about hardware engineers designing real time clocks that count time in HH:MM:SS +
by Gibbon1 3y ago
As an aside dang would probably ban my account if I let rip about what I think about hardware engineers designing real time clocks that count time in HH:MM:SS + day/month/two digit year. And 100 or 128 hz subseconds.
But yeah started using int64 30 years ago and all the fuckedness went away.
- marcosdumay 3y agoYeah, with 64 bits we can go into 1/32768 of second precision and still not get any problem.
- fredoralive 3y agoI suspect the hardware engineer would explain the great favour he’s doing you by handling all the handling of all the weird splits between things like hours, minutes and days for you in hardware logic, rather than you having to waste previous cycles of your MCU’s core to do that sort of thing. But it is indeed a real pain when you want dates in more abstract than human forms…
- JohnFen 3y agoYeah, that hardware engineer isn't really doing anyone any favors.
- JdeBP 3y agoThe rest of us, including a number of hardware engineers who have learned from history, would point to the real-time clock chip that did hardware rules for things right for only one country for a mere three years in the 1980s, until the legislation changed, and whose behaviour has been wrong ever since. Step forward the MC146818, used in the PC/AT and emulated by chipsets since, whose built-in daylight savings time change rule implemented in hardware was rendered obsolete in 1987. http://catless.ncl.ac.uk./Risks/24.60.html#subj12.1 http://catless.ncl.ac.uk./Risks/24.60.html#subj12.1
- Gibbon1 3y agoOld electrical engineer I worked under in the 1980's mentioned he designed a clock calendar STD Bus card. Next design he replaced the whole thing with a 32 bit counter on the processor card and 250 bytes of Z80 assembly. Unrelated I think the lobbyists that got daylight savings time changed charged the BBQ manufacturers $50k.