linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Morton <chromi@cyberspace.org>
To: "Pavel Machek" <pavel@suse.cz>,
	"Michèl Alexandre Salim" <salimma1@yahoo.co.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: Clock drift on Transmeta Crusoe
Date: Tue, 12 Jun 2001 11:26:32 +0100	[thread overview]
Message-ID: <l03130300b74b9ddb0369@[192.168.239.105]> (raw)
In-Reply-To: <20010611223357.A959@bug.ucw.cz>
In-Reply-To: <20010611113604.4073.qmail@web3504.mail.yahoo .com>; from  =?iso-8859-1?Q?Mich=E8l?= Alexandre Salim on Mon, Jun  11, 2001 at  12:36:04PM +0100 <20010611113604.4073.qmail@web3504.mail.yahoo.com>

>> clock drift of a few minutes per day.

That's about 0.1%.  It may be relatively large compared to tolerances of
hardware clocks, but it's realistically tiny.  It certainly compares
favourably with mkLinux on my PowerBook 5300, which usually drifts by
several hours per day regardless of actual load.

The drift might be caused by something masking interrupts for too long, too
often, considering you state that the hardware clock remains comparatively
well-synced.  As another poster suggests, the framebuffer may be to blame.

--------------------------------------------------------------
from:     Jonathan "Chromatix" Morton
mail:     chromi@cyberspace.org  (not for attachments)

The key to knowledge is not to rely on people to teach you it.

GCS$/E/S dpu(!) s:- a20 C+++ UL++ P L+++ E W+ N- o? K? w--- O-- M++$ V? PS
PE- Y+ PGP++ t- 5- X- R !tv b++ DI+++ D G e+ h+ r++ y+(*)



  parent reply	other threads:[~2001-06-12 12:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-11 11:36 Michèl Alexandre Salim
2001-06-11 20:33 ` Pavel Machek
2001-06-12 16:32   ` Alan Cox
2001-06-12 21:00   ` Michèl Alexandre Salim
2001-06-12 22:10     ` Pavel Machek
2001-06-12 10:26 ` Jonathan Morton [this message]
2001-06-12 20:58   ` Michèl Alexandre Salim

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='l03130300b74b9ddb0369@[192.168.239.105]' \
    --to=chromi@cyberspace.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@suse.cz \
    --cc=salimma1@yahoo.co.uk \
    --subject='Re: Clock drift on Transmeta Crusoe' \
    /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

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).