From owner-freebsd-alpha Sat Oct 21 20: 2:57 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 2045037B4D7; Sat, 21 Oct 2000 20:02:53 -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 QAA31383; Sat, 21 Oct 2000 16:05:02 -0700 Date: Sat, 21 Oct 2000 16:00:56 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: John Baldwin Cc: 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 20-Oct-00 John Baldwin wrote: > > jhb 2000/10/20 15:12:18 PDT > > > > Modified files: > > sys/sys kernel.h > > Log: > > Revert the init_clocks change in revision 1.72. On the alpha we use an > > ISA device for our clock, so trying to initialize the clock before probing > > devices introduces a chicken and egg problem. > > > > Debug help from: peter > > > > Revision Changes Path > > 1.74 +2 -2 src/sys/sys/kernel.h > > This should fix the alpha kernels (in theory). This fix is only > temporary however. The clock code on the alpha needs to be restructured > somewhat (most of the clock initialization moved from cpu_initclocks() > 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. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message