Re: get_cmos_time() takes up to a second on boot
From: Andries Brouwer
Date: Mon May 10 2004 - 06:54:36 EST
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
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.
[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?]
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/