| 1 |
On Sat, 15 Dec 2018 17:36:00 +0300 |
| 2 |
Andrew Savchenko <bircoph@g.o> wrote: |
| 3 |
|
| 4 |
> Yes, it is. CONFIG_RTC_HCTOSYS (and CONFIG_RTC_SYSTOHC) is |
| 5 |
> available in kernel for years and should be a preferred way to |
| 6 |
> handle the clock. |
| 7 |
> |
| 8 |
> Best regards, |
| 9 |
> Andrew Savchenko |
| 10 |
|
| 11 |
AFAIK those options still don’t work with RTCs set to local time, do |
| 12 |
they? Which, sadly, are required by anyone who dual-boots with a certain |
| 13 |
other OS made by Microsoft? So hwclock will still be needed for many |
| 14 |
people—perhaps kernel support should be the default, but a painless |
| 15 |
migration path for those who need to keep using hwclock would be |
| 16 |
appropriate (if any migration is even needed—I’m unclear on whether |
| 17 |
hwclock would be removed from the boot runlevel on existing installs or |
| 18 |
only not added on new installs). |
| 19 |
-- |
| 20 |
Christopher Head |
Archives