This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: watchdog - powerpc


>> Or arguably just write a standard watchdog device driver (as lives in 
>> devs/watchdog and uses io/watchdog) and include it in the RedBoot 
>> image.... and if CYGPKG_IO_WATCHDOG isn't defined in <pkgconf/system.h> 
>> just disable the watchdog entirely in SYPCR.
>
>That's what I planned to do. I was just looking for a way to avoid this
>kind of coupling between redboot and the application. Because of the
>write-once nature of the SYPCR register and the watchdog being enabled
>by default, redboot and the application can not decide independently on
>the use of a watchdog.

This is a generic problem actually. Recently code has been added so
that the application can exist back to Redboot. If the application has
started the watchdog, redboot needs to know to take over polling when
the application returns. 

    Andrew

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]