From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <00277185ea730763ab1db50b85fa473b@plan9.bell-labs.com>
From: David Presotto <presotto@closedmind.org>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rio and acme scrolling
In-Reply-To: <609fa6e57786ca89ae54d85144ba7630@plan9.bell-labs.com>
MIME-Version: 1.0
Content-Type: multipart/mixed;
	boundary="upas-yayrzxwwkglmyeuuasrtoijowa"
Date: Sat, 27 Mar 2004 10:12:47 -0500
Topicbox-Message-UUID: 44c90634-eacd-11e9-9e20-41e7f4b1d025

This is a multi-part message in MIME format.
--upas-yayrzxwwkglmyeuuasrtoijowa
Content-Disposition: inline
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit

You always have the local real time clock.  It doesn't tick very
often but is fairly accurate.

	aux/timesync -r

This is the default in termrc.
--upas-yayrzxwwkglmyeuuasrtoijowa
Content-Type: message/rfc822
Content-Disposition: inline

Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Sat Mar 27 10:08:44 EST 2004
Received: from mail.cse.psu.edu ([130.203.4.6]) by plan9; Sat Mar 27 10:08:41 EST 2004
Received: by mail.cse.psu.edu (CSE Mail Server, from userid 60001)
	id EB94919F8E; Sat, 27 Mar 2004 10:08:30 -0500 (EST)
Received: from psuvax1.cse.psu.edu (psuvax1.cse.psu.edu [130.203.4.6])
	by mail.cse.psu.edu (CSE Mail Server) with ESMTP
	id DE2CF19F84; Sat, 27 Mar 2004 10:08:25 -0500 (EST)
X-Original-To: 9fans@cse.psu.edu
Delivered-To: 9fans@cse.psu.edu
Received: by mail.cse.psu.edu (CSE Mail Server, from userid 60001)
	id 28E4A19F84; Sat, 27 Mar 2004 10:07:18 -0500 (EST)
Received: from plan9.cs.bell-labs.com (plan9.bell-labs.com [204.178.31.2])
	by mail.cse.psu.edu (CSE Mail Server) with ESMTP id BCC7B19D7E
	for <9fans@cse.psu.edu>; Sat, 27 Mar 2004 10:07:16 -0500 (EST)
Received: from plan9.cs.bell-labs.com ([135.104.9.2]) by plan9; Sat Mar 27 10:07:16 EST 2004
Received: from plan9.cs.bell-labs.com ([68.36.6.151]) by plan9; Sat Mar 27 10:07:14 EST 2004
Message-ID: <609fa6e57786ca89ae54d85144ba7630@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] rio and acme scrolling
From: Sape Mullender <sape@huygens.org>
In-Reply-To: <466a2993c3a0232a58065be590e2a716@plan9.bell-labs.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Sender: 9fans-admin@cse.psu.edu
Errors-To: 9fans-admin@cse.psu.edu
X-BeenThere: 9fans@cse.psu.edu
X-Mailman-Version: 2.0.11
Precedence: bulk
Reply-To: 9fans@cse.psu.edu
List-Id: Fans of the OS Plan 9 from Bell Labs <9fans.cse.psu.edu>
List-Archive: <https://lists.cse.psu.edu/archives/9fans/>
Date: Sat, 27 Mar 2004 10:07:12 -0500
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on psuvax1.cse.psu.edu
X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.63
X-Spam-Level: 

> The clock (timer 2) speeds up by a factor of 5 or so.
> I can only assume that the firmware uses it for something
> to do with detecting the lid opening again.
> 
> Timesync doesn't change the local hardware, it just
> tweaks the kernel's idea of what time it is and of
> what the clock frequency is.  It would cope with
> the clock change except that I made timesync ignore any huge
> swings (anything more than 25%) because I had assumed that
> would only be the result of a samplng mistake.
> 
> I changed the limits and timesync will now put up with such a
> change, though it will take some minutes to latch onto
> the exact new value (needs enough of a time base to
> compare to).
> 
> Tell me if this is a problem.  Short of actually
> implementing ACPI, I think this is as good as we can
> do.

Does this work if timesync doesn't have an external time source to synchronize to?

	Sape

--upas-yayrzxwwkglmyeuuasrtoijowa--