From owner-freebsd-hackers  Mon May  3 20:20:58 1999
Delivered-To: freebsd-hackers@freebsd.org
Received: from home.dragondata.com (home.dragondata.com [204.137.237.2])
	by hub.freebsd.org (Postfix) with ESMTP id 81E08156B3
	for <hackers@FreeBSD.ORG>; Mon,  3 May 1999 20:20:52 -0700 (PDT)
	(envelope-from toasty@home.dragondata.com)
Received: (from toasty@localhost)
	by home.dragondata.com (8.9.2/8.9.2) id WAA09953;
	Mon, 3 May 1999 22:20:43 -0500 (CDT)
From: Kevin Day <toasty@home.dragondata.com>
Message-Id: <199905040320.WAA09953@home.dragondata.com>
Subject: Re: Clock code patch sought.
In-Reply-To: <Pine.BSF.3.95.990503201102.9332C-100000@current1.whistle.com> from Julian Elischer at "May 3, 1999  8:13:47 pm"
To: julian@whistle.com (Julian Elischer)
Date: Mon, 3 May 1999 22:20:42 -0500 (CDT)
Cc: hackers@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL43 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> There was a patch floating around that re-read the clock registers several
> times for broken hardware, to get rid of the problems of user time going
> backwards due to misreads.
> 
> I have been unable to find exact references in the archives..
> does anyone remember the patches in question?
> 
> It was within the last year..
> 
> julian
> 
> 

http://www.freebsd.org/cgi/query-pr.cgi?pr=6630

Take a look.

I had to modify it to do 4 reads, instead of 2 though.


Kevin


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message