Subject: Re: hardclock(9) for cobalt
To: None <port-cobalt@netbsd.org>
From: Izumi Tsutsui <tsutsui@ceres.dti.ne.jp>
List: port-cobalt
Date: 07/30/2004 22:19:13
In article <000701c47636$4c0034d0$0d00a8c0@paq5>
locore32@gaea.ocn.ne.jp wrote:

> > Because the timer is already running when _splnone() is called
> > in cpu_configure()?
> 
> Other ports do the same way.  Why does cobalt make trouble in
> this certain way?

Because timers are started (or timer interrupts are enabled or established)
in cpu_initclocks(9) (which is called from initclocks() after
softclock_si is initialized) on other ports.
(or no generic soft interrupts on some ports?)
---
Izumi Tsutsui
tsutsui@ceres.dti.ne.jp