From: "Iain Sandoe" <iain@sandoe.co.uk>
To: Gabriel Paubert <paubert@iram.es>,
Geert Uytterhoeven <geert@linux-m68k.org>
Cc: benjamin herrenschmidt <bh40@calva.net>,
martin costabel <costabel@wanadoo.fr>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: rtc again...
Date: Tue, 08 Aug 2000 12:35:10 +0100 [thread overview]
Message-ID: <200008081137.MAA10748@hyperion.valhalla.net> (raw)
On Tue, Aug 8, 2000, Gabriel Paubert wrote:
> On Fri, 4 Aug 2000, Geert Uytterhoeven wrote:
>
>> > Actually given the problems with RTC being UTC or local time, the offset
>> > might perhaps better be setup as a kernel parameter so that th system
>> > start up in a known good state. It seems that it is in RAM for Macs, but
>> > what about other machines (I have no problems since all my machines are
>> > UTC and I simply refuse to use an OS which requires anything else) ?
>>
>> Why do you want to handle the offset in the kernel???
>>
>> Any decent distro (e.g. Debian) allows to configure the time system for a
>> hardware clock running in either UTC or local time, so the correction will be
>> done on boot up.
>>
>
> I think there is some misunderstanding here. I don't want to handle the
> offset in the kernel, with one possible exception: when reading the
> RTC for the first time to initialize xtime. Getting timestamps right as early
> as possible might be important in some cases, and it's not a big deal
> since the code to do this is small and thrown away anyway.
>
> Oh and I can't remember whether the clock or hwclock command ever worked
> on my machines. I think hwclock did once upon a time; life is so much
> simpler with NTP anyway (but it is run quite late in the boot process,
> actually just before the rc.local script on most of my machines and after
> mounting NFS file systems and starting daemons like syslogd/crond/inetd).
I seems to me (in summary) [since I started this thread :-) ]:
we can:
(a) Fix up time in the kernel to emulate UTC
(b) Fix up time in the kernel to emulates Local Time
Which (or will both) of these works with hwclock (since that is the
mechanism at 2.4.0 ?) and for those of us switching to-and-ffo is also
being used at 2.2.17
I would like to make sure that timestamps are right during kernel boot -
and, at the moment, when using 2.2.17 I have to 'artificially' disable rtc
to get the correct time.
For many (paid-by-the-call) telephone network users NTP is not a suitable
option - they don't like the machine making calls without asking.
Iain.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-08-08 11:35 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-08-08 11:35 Iain Sandoe [this message]
2000-08-08 13:14 ` rtc again Geert Uytterhoeven
-- strict thread matches above, loose matches on Subject: below --
2000-08-08 14:31 Iain Sandoe
2000-08-08 17:08 ` Michael Schmitz
2000-08-08 17:41 ` Benjamin Herrenschmidt
2000-08-08 22:44 ` Gabriel Paubert
2000-08-09 8:44 ` Benjamin Herrenschmidt
2000-08-09 11:32 ` Martin Costabel
2000-08-09 13:50 ` Gabriel Paubert
2000-08-09 15:25 ` Benjamin Herrenschmidt
2000-08-09 16:54 ` Takashi Oe
2000-08-09 17:04 ` Benjamin Herrenschmidt
2000-08-09 23:12 ` Takashi Oe
2000-08-09 23:48 ` Benjamin Herrenschmidt
2000-08-09 22:13 ` Gabriel Paubert
2000-08-09 22:48 ` Benjamin Herrenschmidt
2000-08-10 3:08 ` Gabriel Paubert
2000-08-10 0:00 ` William Blew
2000-08-09 14:26 ` Takashi Oe
2000-08-09 0:55 ` Takashi Oe
2000-08-09 8:48 ` Benjamin Herrenschmidt
2000-08-09 16:37 ` Takashi Oe
2000-08-09 22:46 ` Gabriel Paubert
2000-08-09 14:24 ` Geert Uytterhoeven
[not found] <20000804205524.383@192.168.1.10>
2000-08-05 1:10 ` Takashi Oe
2000-08-05 11:25 ` Benjamin Herrenschmidt
2000-08-05 14:44 ` Takashi Oe
2000-08-03 11:24 Iain Sandoe
2000-08-03 9:56 Iain Sandoe
2000-08-03 10:13 ` Benjamin Herrenschmidt
2000-08-03 11:58 ` Martin Costabel
2000-08-03 9:41 Iain Sandoe
2000-08-02 22:48 Iain Sandoe
2000-08-03 9:00 ` Martin Costabel
2000-08-03 9:30 ` Benjamin Herrenschmidt
2000-08-03 10:54 ` Gabriel Paubert
2000-08-03 11:14 ` Benjamin Herrenschmidt
2000-08-03 11:25 ` Gabriel Paubert
2000-08-03 11:45 ` Gabriel Paubert
2000-08-03 13:25 ` Benjamin Herrenschmidt
2000-08-03 23:33 ` Takashi Oe
2000-08-04 8:55 ` Gabriel Paubert
2000-08-04 15:25 ` David Edelsohn
2000-08-04 15:50 ` Benjamin Herrenschmidt
2000-08-07 12:33 ` Gabriel Paubert
2000-08-07 11:51 ` Gabriel Paubert
2000-08-07 13:18 ` Benjamin Herrenschmidt
2000-08-07 15:14 ` David Edelsohn
2000-08-07 21:16 ` Gabriel Paubert
2000-08-08 1:39 ` Paul Mackerras
2000-08-11 11:04 ` Gabriel Paubert
2000-08-12 6:29 ` Paul Mackerras
2000-08-12 12:02 ` Ethan Benson
2000-08-12 12:51 ` Gabriel Paubert
2000-08-12 18:46 ` Gabriel Paubert
2000-08-14 12:59 ` Gabriel Paubert
[not found] ` <Pine.LNX.3.96LJ1.1b7.1000803182949.650C-100000@ofey.earthl ink.net>
2000-08-03 23:58 ` Franz Sirl
2000-08-04 0:33 ` Takashi Oe
2000-08-04 12:54 ` Benjamin Herrenschmidt
2000-08-04 13:40 ` Takashi Oe
2000-08-04 13:20 ` Geert Uytterhoeven
2000-08-08 11:20 ` Gabriel Paubert
2000-08-03 10:31 ` Franz Sirl
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=200008081137.MAA10748@hyperion.valhalla.net \
--to=iain@sandoe.co.uk \
--cc=bh40@calva.net \
--cc=costabel@wanadoo.fr \
--cc=geert@linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paubert@iram.es \
/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).