From owner-freebsd-alpha Mon Mar 5 10:30:21 2001 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4ABDF37B719 for ; Mon, 5 Mar 2001 10:30:19 -0800 (PST) (envelope-from mjacob@feral.com) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id KAA03603; Mon, 5 Mar 2001 10:30:17 -0800 Date: Mon, 5 Mar 2001 10:30:15 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Yoriaki FUJIMORI Cc: freebsd-alpha@freebsd.org Subject: Re: My list of -CURRENT problems In-Reply-To: <200103051823.f25INdT38459@baron.fujimori.cache.waseda.ac.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > As for a realtime clock problem, it should persist on many alphapc164, > pc164lx and up1100. At least in my lab, they all suffer from this. > It was a fun to see `Feb 29, 2000' on all of them. (;_;) > > I guess FreeBSD/Alpha alone makes use of mcclock.c. I could not find > its counterpart in FreeBSD/i386. that's correct. it's a non-Y2K compliant chip that is only on digital machines To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message