On 01/12/2015 at 20:49:19 +0100, Uwe Kleine-König wrote : > > Seeing the comment comment above, this should probably be if > > (tm->tm_year < 100 || tm->tm_year >= 200) > > I don't think this particular part has any issue > > handling 2038. However, on 32bit platform, your userspace is probably > > not ready to handle those date. hwclock should return the correct date. > > userspace is not ready because it cannot. Before this can be addressed, > quite some things need fixing first. If I understood correctly timerfd > for example is broken which completely locks up systemd. > > Note this doesn't justify to not write a date later than 2037 in the rtc > driver however. Still thinking about how to handle this for the machines > we work on, we thought about letting the RTC_RD_TIME ioctl fail for > dates later than 2038 to work around this issue. > Yeah but the rtc doesn't have any issue handling dates after 2038 so if it is used on a 64bit system, it can work properly until february 2100. Also, I'm not sure how that solves your problem anyway. -- Alexandre Belloni, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
