From owner-freebsd-alpha Sun Oct 22 12:17:18 2000 Delivered-To: freebsd-alpha@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 813CE37B479; Sun, 22 Oct 2000 12:17:14 -0700 (PDT) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id MAA01658; Sun, 22 Oct 2000 12:17:11 -0700 Date: Sun, 22 Oct 2000 12:14:24 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: Doug Rabson 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 Yes, I know that... > 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. Right- that's what I was going to look at today or tomorrow. I've had a lot of DSL outages so I haven't made as much progress as I'd like. BTW- most excellent to see the 2 of you at BSDcon.... -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message