From: Russell King - ARM Linux > Sent: 20 June 2017 22:16 .. > Consider that at the moment, we define the 32-bit RTC representation to > start at a well known epoch. We _could_ decide that when it wraps to > 0x80000000 seconds, we'll define the lower 0x40000000 seconds to mean > dates in the future - and keep rolling that forward each time we cross > another 0x40000000 seconds. Unless someone invents a real time machine, > we shouldn't need to set a modern RTC back to 1970. True, just treating the value as unsigned gives another 67 years. If a 32bit RTC is programmed with the low 32bits of the 64bit 'seconds since 1970' the kernel should have no real difficulty sorting out the high bits from other available information. Problems with things like the x86 bios setting the rtc to stupid values are another matter. ISTR the rtc chip has a bit for 'summertime' that is never set, on a multi-os system you can get multiple summer time changes. David -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
