This is the mail archive of the
ecos-devel@sources.redhat.com
mailing list for the eCos project.
Re: sh implementation
- From: Jonathan Larmour <jifl at eCosCentric dot com>
- To: "Suzuki, RyosIII" <ryos at sinby dot com>
- Cc: ecos-devel at sources dot redhat dot com
- Date: Tue, 09 Sep 2003 04:25:35 +0100
- Subject: Re: sh implementation
- References: <200309060208.EIJ51990.ZTSP@sinby.com>
Suzuki, RyosIII wrote:
Hello all,
I have a question about HAL_RESET_CLOCK and HAL_INTERRUPT_
ACKNOWREDGE in sh implementation.
it seems sh's HAL_RESET_CLOCK clears interrupt cause. and
HAL_INTERRUPT_ACKNOWREDGE does nothing. but in other
architectures, mips, arm, sparc, i386 ... I see
HAL_RESET_CLOCK is used to reset clock counter not to clear
interrupt cause. HAL_INTERRUPT_ACKNOWREDGE is used to clear
interrupt cause.
I feel that sh implementation is different from others.
why?
I believe simply because it's hardware specific, and since the SH
implementation uses the same on-chip clock everywhere, that's what it's in
the arch HAL. So the HAL_CLOCK_RESET implementation just reflects what the
hardware requires. Other hardware may have different requirements.
Oh, and as far I can see, all SH implementations of
HAL_INTERRUPT_ACKNOWLEDGE do do something.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine