From owner-freebsd-alpha Sun Oct 22 12:11:12 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from anchor-post-33.mail.demon.net (anchor-post-33.mail.demon.net [194.217.242.91]) by hub.freebsd.org (Postfix) with ESMTP id DA4D137B479; Sun, 22 Oct 2000 12:11:08 -0700 (PDT) Received: from nlsys.demon.co.uk ([158.152.125.33] helo=herring.nlsystems.com) by anchor-post-33.mail.demon.net with esmtp (Exim 2.12 #1) id 13nQWQ-000GWW-0X; Sun, 22 Oct 2000 20:11:07 +0100 Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id UAA40481; Sun, 22 Oct 2000 20:14:35 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Sun, 22 Oct 2000 20:14:35 +0100 (BST) From: Doug Rabson To: Matthew Jacob Cc: John Baldwin , alpha@freebsd.org, cvs-all@freebsd.org, cvs-committers@freebsd.org Subject: RE: cvs commit: src/sys/sys kernel.h In-Reply-To: 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 On Sat, 21 Oct 2000, Matthew Jacob wrote: > > to clock_attach() and using the cpu clock interrupt to trigger hardclock() > > during the device probe) and then this change can be un-reverted. > > Hmm. This is what I'd been thinking might be the case. However, not > all alphas use an ISA clock. We'll see. As soon as my DSL comes back up (when > you'll see this mail, likely) I'll update and try and see where we're at. All platforms, including ones without an ISA clock will deliver clock interrupts at the advertised frequency from PALcode. All we need is something to tick the scheduler during device probes - when the real clock attaches, we will calibrate things and install timecounters etc. -- Doug Rabson Mail: dfr@nlsystems.com Phone: +44 20 8348 6160 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message