Re: CONFIG_RTC_HCTOSYS lost on x86 with ALWAYS_USE_PERSISTENT_CLOCKchanges?
From: Alexander Holler
Date: Wed Apr 24 2013 - 01:12:48 EST
Am 24.04.2013 05:19, schrieb John Stultz:
On x86 the persistent_clock() is backed by the
CMOS/EFI/kvm-wall/xen/vrtc clock (all via x86_platform.get_wallclock)
should be present and we'll initialize the time in timekeeping_init()
Its only systems where there isn't a persistent_clock is where the RTC
layer and the HCTOSYS is helpful.
I'm a bit confused too. ;)
Doesn't this remove the users choice of RTC on x86 systems?
Why is there a difference made between the CMOS/EFI/... clocks and other
And why is RTC_SYSTOHC now gone on x86?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/