Date: Sat, 21 Oct 2000 23:19:08 -0700 (PDT) From: Matthew Jacob <mjacob@feral.com> To: John Baldwin <jhb@FreeBSD.ORG> Cc: alpha@FreeBSD.ORG, cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG Subject: RE: cvs commit: src/sys/sys kernel.h Message-ID: <Pine.BSF.4.21.0010212318220.1105-100000@beppo.feral.com> In-Reply-To: <Pine.LNX.4.21.0010211559580.762-100000@zeppo.feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
This (may have) caused my PC164 to now boot. I'll look into what you suggest tomorrow. On Sat, 21 Oct 2000, Matthew Jacob wrote: > > > > > > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0010212318220.1105-100000>