[ECOS] HAL macros and RTC

Fabrice Gautier Fabrice_Gautier@sdesigns.com
Tue Jan 28 04:07:00 GMT 2003


> -----Original Message-----
> From: Gary Thomas [mailto:gary@mlbassoc.com]
> Subject: Re: [ECOS] HAL macros and RTC
> 
> 
> The platforms define CYGNUM_HAL_INTERRUPT_xxx and they are very
> much platform specific.  CYGNUM_HAL_INTERRUPT_RTC is the one 
> interrupt which must be defined by a platform for the heartbeat
> clock/timer, thus the platform neutral name.
> 
> Is this not how you expected it to work?

Well, I was just suggesting to change the name of the macros, because i got
confused.
What make  CYGNUM_HAL_INTERRUPT_RTC more platform neutral than say
CYGNUM_HAL_INTERRUPT_UART0 and the others ? 

When I started my port, I listed my interrupt vectors and called them
CYGNUM_HAL_INTERRUPT_xxx, and one of them is for an hardware Clock so i just
named it CYGNUM_HAL_INTERRUPT_RTC. And then everything compiled fine and
redboot runs, i didnt realized that CYGNUM_HAL_INTERRUPT_RTC was more
special than the other CYGNUM_HAL_INTERRUPT_xxx until i tried to do
multitasking.  

So thats why i'm suggestion another name like CYGNUM_KERNEL_RTC_VECTOR (or
whatever is judged appropriate) maybe change the other names to
CYGNUM_HAL_myarch_INTERRUPT_xxx (but they are many more)... 

But It's not that important...

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss



More information about the Ecos-discuss mailing list