From owner-freebsd-hackers Sat Feb 12 19:30:19 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from overcee.netplex.com.au (overcee.netplex.com.au [202.12.86.7]) by builder.freebsd.org (Postfix) with ESMTP id 2BE6D4417 for ; Sat, 12 Feb 2000 19:30:12 -0800 (PST) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id DBB531CD9; Sun, 13 Feb 2000 11:30:13 +0800 (WST) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Brian Beattie Cc: hackers@FreeBSD.ORG Subject: Re: CMOS clock won't do 2000 In-Reply-To: Message from Brian Beattie of "Sat, 12 Feb 2000 12:57:46 PST." Date: Sun, 13 Feb 2000 11:30:13 +0800 From: Peter Wemm Message-Id: <20000213033013.DBB531CD9@overcee.netplex.com.au> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Brian Beattie wrote: > I have an older 486 system, running 3.4R that has a cmos clock that seems > to be unwilling to accept years out side the range 94-99. The bios seems > willing to set dates between 1994-2099, but after reboot any year not > between 94-99 is converted to {20,19}94. > > What I have done is to go into i386/isa/clock.c and in the routines > inittodr, resettodr, is to add 6 to and subtract 6 from the years > respectively. I was wondering if anybody had any better ideas. Also watch out for day-of-month and day-of-week calulations done in the cmos chip. It's a shame you couldn't set it for 1972 which matches the year 2000 date, day, and leap year sequences exactly. Cheers, -Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message