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/31/2004 21:32:59
> Why does cobalt make trouble in this certain way?
I've just started thinking of another reasoning than hardclock theory.
(I admit my first response was derived from wrong consequence)
With MIPS processor softclock is handled with real interrupt context.
Is it the cause of this particular device driver issue?
Toru Nishimura/ALKYL Technology