From: Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>
To: Kurt Roeckx <Q@ping.be>,
Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>
Cc: Riley Williams <rhw@MemAlpha.cx>, Pavel Machek <pavel@suse.cz>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Alex Bligh - linux-kernel <linux-kernel@alex.org.uk>
Subject: Re: PROBLEM: Linux updates RTC secretly when clock synchronizes
Date: Wed, 07 Nov 2001 01:15:29 -0000 [thread overview]
Message-ID: <814537660.1005095728@[195.224.237.69]> (raw)
In-Reply-To: <20011107020137.A1887@ping.be>
In-Reply-To: <20011107020137.A1887@ping.be>
>> > 2. The kernel makes no internal reference to the /dev/rtc driver,
>> > and it is left to userland tools to sync to the RTC on boot,
>> > and at other times as required.
>>
>> I think the kernel should set the machine time to the RTC time
>> as an initializer on boot. Other than that, I agree.
>
> Which is something you do from userspace.
You have to initialize (once, on boot) this to
something. I don't really see the point of initializing
it to zero and putting the atime/mtime on a few entries
back to 1970, when we have the value there already.
We /know/ we have to use the RTC values for things
like apm suspend, for instance - I don't want my 'make'
to be broken through races with userspace time functions -
so if we are prepared to read RTC on resume, we should be
prepared to read RTC on boot.
--
Alex Bligh
next prev parent reply other threads:[~2001-11-07 1:16 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-31 0:33 PROBLEM: Linux updates RTC secretly when clock synchronizes Ian Maclaine-cross
2001-10-31 1:05 ` Kurt Roeckx
2001-10-31 2:55 ` Ian Maclaine-cross
2001-10-31 11:52 ` Kurt Roeckx
2001-11-01 0:52 ` Riley Williams
2001-11-01 1:26 ` Kurt Roeckx
2001-11-01 13:57 ` Alex Bligh - linux-kernel
2001-11-02 9:50 ` Riley Williams
2001-11-03 11:41 ` Alex Bligh - linux-kernel
2001-11-03 18:35 ` Riley Williams
2001-11-03 19:19 ` Alex Bligh - linux-kernel
2001-11-03 21:04 ` Kurt Roeckx
2001-11-06 10:01 ` Pavel Machek
2001-11-06 9:57 ` Pavel Machek
2001-11-02 12:16 ` Pavel Machek
2001-11-05 23:08 ` Riley Williams
2001-11-06 10:17 ` Pavel Machek
2001-11-07 0:00 ` Riley Williams
2001-11-07 0:44 ` Alex Bligh - linux-kernel
2001-11-07 1:01 ` Kurt Roeckx
2001-11-07 1:15 ` Alex Bligh - linux-kernel [this message]
2001-11-07 9:24 ` Russell King
2001-11-08 12:26 ` Pavel Machek
2001-11-08 23:00 ` Riley Williams
2001-11-09 9:32 ` Pavel Machek
2001-11-09 21:11 ` Riley Williams
2001-11-09 21:30 ` Pavel Machek
2001-11-09 22:54 ` Riley Williams
2001-11-09 23:10 ` Mark Zealey
2001-11-10 20:04 ` Pavel Machek
2001-11-10 20:35 ` Riley Williams
2001-11-10 20:43 ` Pavel Machek
2001-11-10 20:49 ` Doug McNaught
2001-11-06 0:20 ` Ian Maclaine-cross
2001-11-06 10:18 ` Pavel Machek
2001-11-08 5:09 ` Ian Maclaine-cross
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='814537660.1005095728@[195.224.237.69]' \
--to=linux-kernel@alex.org.uk \
--cc=Q@ping.be \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=rhw@MemAlpha.cx \
/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).