This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: HAL macros and RTC
- From: Nick Garnett <nickg at ecoscentric dot com>
- To: Fabrice Gautier <Fabrice_Gautier at sdesigns dot com>
- Cc: 'Jonathan Larmour' <jifl at eCosCentric dot com>,'Gary Thomas' <gary at mlbassoc dot com>,"Ecos-List (E-mail)" <ecos-discuss at sources dot redhat dot com>
- Date: 29 Jan 2003 17:16:18 +0000
- Subject: Re: [ECOS] HAL macros and RTC
- References: <9F77D654ED40B74CA79E5A60B97A087B0423EC@sd-exchange.sdesigns.com>
Fabrice Gautier <Fabrice_Gautier@sdesigns.com> writes:
>
> I dont know if the "on core timer" is always plugged into the same IRQ line
> for MIPS or PPC,
It is, it's part of the architecture definition.
> but thats not the case for me. I think we should have in
> the guide:
>
> "You only have to calculate and enter the proper CYGNUM_HAL_RTC_CONSTANTS
> definitions in the platform CDL file and define CYGNUM_HAL_INTERRUPT_RTC in
> [some include file]"
Good point, I'll take a look at doing that.
>
> By the way shouldnt the interrupt be a CDL option like the other RTC related
> constants ?
Not really. The interrupt used is fixed by the hardware of the timer,
usually. If a particular platform provided several timers, and if the
HAL implementor chose to allow a choice, then indeed this value might
need to change along with the definitions of the HAL_CLOCK_*()
macros.
--
Nick Garnett - eCos Kernel Architect
http://www.eCosCentric.com/
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss