Subject: Re: hardclock(9) for cobalt
To: None <port-cobalt@netbsd.org>
From: Toru Nishimura <locore32@gaea.ocn.ne.jp>
List: port-cobalt
Date: 07/30/2004 22:08:24 
>> no matter how TIMER0 value of GT64011 is set.
>
> 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?

Toru Nishimura/ALKYL Technology