From: David Brownell <david-b@pacbell.net>
To: Alessandro Zummo <alessandro.zummo@towertech.it>
Cc: akpm@osdl.org, linuxppc-dev@ozlabs.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ralf@linux-mips.org, Andi Kleen <ak@muc.de>,
lethal@linux-sh.org, paulus@samba.org, rmk@arm.linux.org.uk,
davem@davemloft.net, kkojima@rr.iij4u.or.jp
Subject: Re: NTP time sync
Date: Wed, 22 Nov 2006 11:55:23 -0800 [thread overview]
Message-ID: <200611221155.26686.david-b@pacbell.net> (raw)
In-Reply-To: <20061122203633.611acaa8@inspiron>
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
WARNING: multiple messages have this Message-ID (diff)
From: David Brownell <david-b@pacbell.net>
To: Alessandro Zummo <alessandro.zummo@towertech.it>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linuxppc-dev@ozlabs.org, Kumar Gala <galak@kernel.crashing.org>,
Kim Phillips <kim.phillips@freescale.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Andi Kleen <ak@muc.de>,
akpm@osdl.org, davem@davemloft.net, kkojima@rr.iij4u.or.jp,
lethal@linux-sh.org, paulus@samba.org, ralf@linux-mips.org,
rmk@arm.linux.org.uk
Subject: Re: NTP time sync
Date: Wed, 22 Nov 2006 11:55:23 -0800 [thread overview]
Message-ID: <200611221155.26686.david-b@pacbell.net> (raw)
In-Reply-To: <20061122203633.611acaa8@inspiron>
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
next prev parent reply other threads:[~2006-11-22 20:02 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-22 19:36 NTP time sync Alessandro Zummo
2006-11-22 19:36 ` Alessandro Zummo
2006-11-22 19:51 ` Russell King
2006-11-22 19:51 ` Russell King
2006-11-22 20:26 ` Alessandro Zummo
2006-11-22 20:26 ` Alessandro Zummo
2006-11-22 19:55 ` David Brownell [this message]
2006-11-22 19:55 ` David Brownell
2006-11-22 20:23 ` Alessandro Zummo
2006-11-22 20:23 ` Alessandro Zummo
2006-11-23 1:48 ` Gabriel Paubert
2006-11-23 1:48 ` Gabriel Paubert
2006-11-23 10:54 ` Andi Kleen
2006-11-23 10:54 ` Andi Kleen
2006-11-23 11:00 ` Benjamin Herrenschmidt
2006-11-23 11:00 ` Benjamin Herrenschmidt
2006-11-25 23:22 ` David Brownell
2006-11-25 23:22 ` David Brownell
2006-11-26 11:04 ` Joakim Tjernlund
2006-11-26 11:04 ` Joakim Tjernlund
2006-11-26 19:21 ` Alessandro Zummo
2006-11-26 19:21 ` Alessandro Zummo
2006-11-26 21:37 ` Joakim Tjernlund
2006-11-26 21:37 ` Joakim Tjernlund
2006-11-26 22:06 ` Michael Raskin
2006-11-26 22:53 ` Alessandro Zummo
2006-11-26 22:53 ` Alessandro Zummo
2006-11-27 1:21 ` [Bulk] " David Brownell
2006-11-27 1:21 ` David Brownell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200611221155.26686.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=alessandro.zummo@towertech.it \
--cc=davem@davemloft.net \
--cc=kkojima@rr.iij4u.or.jp \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
--cc=ralf@linux-mips.org \
--cc=rmk@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.