From: Andries Brouwer <aebr@win.tue.nl>
To: Gabriel Paubert <paubert@iram.es>
Cc: Linus Torvalds <torvalds@osdl.org>,
Tim Bird <tim.bird@am.sony.com>,
linux-kernel@vger.kernel.org
Subject: Re: get_cmos_time() takes up to a second on boot
Date: Mon, 10 May 2004 13:53:18 +0200 [thread overview]
Message-ID: <20040510115318.GA8632@wsdw14.win.tue.nl> (raw)
In-Reply-To: <20040510105230.GA14104@iram.es>
On Fri, May 07, 2004 at 07:15:53PM -0700, Linus Torvalds wrote:
>> These days, I think we do the write-back only if we use an external clock
>> (NTP), so we probably _could_ just remove the synchronization at
>> read-time (removing it at write-time doesn't sound like a good idea).
>>
>> I don't think we should necessarily disable the synchronization, but we
>> could certainly make it optional for cases that don't care about it. We
>> might even make the default be "don't care about the read
>> synchronization".
On Mon, May 10, 2004 at 12:52:30PM +0200, Gabriel Paubert wrote:
> I'm for one against dropping the synchronization and even making the
> default not to synchronize, I'd rather see this as an option under
> the embedded subset for the people who really want fast boot time.
There is hwclock that will read or write the CMOS clock,
and it synchronizes.
So if one wants to synchronize with the CMOS clock (rather than, say,
with an external clock), and wants the better-than-1-sec accuracy,
then that can be done in a boot script.
Andries
[I think everybody likes fast boot time.
Ah - 30 years ago my system booted in the fraction of a second
needed to print the command prompt.
Why have computers become so slow?]
prev parent reply other threads:[~2004-05-10 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-08 0:41 Tim Bird
2004-05-08 2:15 ` Linus Torvalds
2004-05-10 6:05 ` Matthias Urlichs
2004-05-10 10:52 ` Gabriel Paubert
2004-05-10 11:53 ` Andries Brouwer [this message]
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=20040510115318.GA8632@wsdw14.win.tue.nl \
--to=aebr@win.tue.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=paubert@iram.es \
--cc=tim.bird@am.sony.com \
--cc=torvalds@osdl.org \
/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
all inboxes | Powered by JetHome®