| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <CAPXgP128yAq1jju-gsZcaS-mZPt+7tq0tt-uVk3Yqr77abd26Q@mail.gmail.com> Date: Wed, 24 Apr 2013 05:05:18 +0200 From: Kay Sievers <kay@...y.org> To: John Stultz <john.stultz@...aro.org> Cc: LKML <linux-kernel@...r.kernel.org> Subject: Re: CONFIG_RTC_HCTOSYS lost on x86 with ALWAYS_USE_PERSISTENT_CLOCK changes? On Wed, Apr 24, 2013 at 4:43 AM, John Stultz <john.stultz@...aro.org> wrote: > On 04/23/2013 06:34 PM, Kay Sievers wrote: >> >> Hey, >> >> what's the intention of: >> e90c83f757fffdacec8b3c5eee5617dcc038338f ? >> x86: Select HAS_PERSISTENT_CLOCK on x86 >> >> It unconditionally sets: >> HAS_PERSISTENT_CLOCK >> but: >> RTC_SYSTOHC >> got a depends on !HAS_PERSISTENT_CLOCK >> >> This makes it impossible to sync the system time from the RTC on x86. >> What's going on here? > > > So I suspect just some confusion, but let me know if thats wrong and you're > actually seeing an issue. > > SYSTOHC is what *sets the RTC* to the system time when we're synced with > NTP. > > HCTOSYS is what sets the system time from the RTC. Right, and RTC_HCTOSYS is not NTP related. It just reads the time from the RTC_HCTOSYS_DEVICE at bootup so we do not boot in 1970 time mode. We need that it in all cases, at every bootup on x86. But it's no longer there with the above commits. :) Kay -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists