From: Richard Zidlicky <rz@linux-m68k.org>
To: Gabriel Paubert <paubert@iram.es>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Wolfgang Denk <wd@denx.de>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: set_rtc_time() cleanup / normalization
Date: Tue, 13 May 2003 14:03:51 +0200 [thread overview]
Message-ID: <20030513120351.GB3868@linux-m68k.org> (raw)
In-Reply-To: <20030513081817.A25655@mrt-lx1.iram.es>
> > On m68k, we removed that part because it confused NTP. Richard Zidlicky can
> > probably tell more about that.
more specific, syncinc systime with NTP could confuse hwclock,
see eg the thread following
http://marc.theaimsgroup.com/?l=linux-kernel&m=100448857801670&w=2
Although workarounds are possible, there are some more reasons
to dislike the hwclk update code in arch/*kernel/time.c:
- RTC should be accessed by proper rtc device driver only
- magic updates may confuse hwclock, adjtimex and other programs,
some programs need to use workarounds to avoid triggering it.
- everything it does can be done much better by userspace
accessing /dev/rtc
- implements policy and thus doesn´t belong into kernel
- getting rid of it saves a few clock cycles on every timer
interrupt
- nobody can positively expect it to work, iirc many HW
variants were never supported -> nothing can break if
it is killed
Richard
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-05-13 12:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-12 21:17 set_rtc_time() cleanup / normalization Wolfgang Denk
2003-05-13 0:16 ` Dan Malek
2003-05-13 7:52 ` Geert Uytterhoeven
2003-05-13 8:18 ` Gabriel Paubert
[not found] ` <Pine.GSO.4.21.0305131051420.20323-100000@vervain.sonytel.be>
2003-05-13 10:21 ` Gabriel Paubert
2003-05-13 13:35 ` Wolfgang Denk
2003-05-13 12:03 ` Richard Zidlicky [this message]
2003-05-13 23:05 ` Paul Mackerras
2003-05-13 23:33 ` Eugene Surovegin
2003-05-14 0:08 ` Wolfgang Denk
[not found] ` <5.1.0.14.2.20030513171616.037f6800@mail.ebshome.net>
2003-05-14 3:47 ` Matt Porter
[not found] ` <5.1.0.14.2.20030513214040.02a6e6d0@mail.ebshome.net>
[not found] ` <3EC1DB1F.8000408@embeddededge.com>
2003-05-14 6:41 ` Eugene Surovegin
2003-05-14 6:47 ` Wolfgang Denk
2003-05-14 8:32 ` Benjamin Herrenschmidt
2003-05-14 15:57 ` Gabriel Paubert
2003-05-14 16:41 ` Eugene Surovegin
2003-05-14 15:50 ` Gabriel Paubert
2003-05-14 15:43 ` Gabriel Paubert
2003-05-14 16:28 ` Dan Malek
2003-05-15 18:04 ` Gabriel Paubert
2003-05-15 18:21 ` Wolfgang Denk
[not found] ` <20030515184412.GA22327@iram.es>
2003-05-15 19:37 ` Benjamin Herrenschmidt
[not found] <20030514230638.GB1687@linux-m68k.org>
[not found] ` <Pine.GSO.4.21.0305151031410.13683-100000@vervain.sonytel.be>
2003-05-15 10:45 ` Gabriel Paubert
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=20030513120351.GB3868@linux-m68k.org \
--to=rz@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paubert@iram.es \
--cc=wd@denx.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).