[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200611221155.26686.david-b@pacbell.net>
Date: Wed, 22 Nov 2006 11:55:23 -0800
From: David Brownell <david-b@...bell.net>
To: Alessandro Zummo <alessandro.zummo@...ertech.it>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
linuxppc-dev@...abs.org, Kumar Gala <galak@...nel.crashing.org>,
Kim Phillips <kim.phillips@...escale.com>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Andi Kleen <ak@....de>, akpm@...l.org, davem@...emloft.net,
kkojima@...iij4u.or.jp, lethal@...ux-sh.org, paulus@...ba.org,
ralf@...ux-mips.org, rmk@....linux.org.uk
Subject: Re: NTP time sync
On Wednesday 22 November 2006 11:36 am, Alessandro Zummo wrote:
>
> wrto the in-kernel NTP synchronization,
> as discussed before [1], my opinion
> is that it should be done in userland.
>
> Keeping it in kernel implies subtle code
> in each of the supported architectures.
>
> So, if the arch maintainers agree,
> I would suggest to schedule it for removal.
>
> [1] http://lkml.org/lkml/2006/3/28/358
Suggested time of removal: one year after two relevant software
package releases get updated:
- NTPD, to call hwclock specifying the relevant RTC;
- util-linux, updating hwclock to know about /dev/rtcN;
- busybox, with its own hwclock implementation.
The util-linux hwclock update is already in the queue, I'm told.
- Dave
-
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