/dev/watchdog for onchip MPC860 watchdog?
dan at netx4.com
Thu Oct 21 03:47:22 EST 1999
Jeff Millar wrote:
> If the boot process goes bad, then the interrupt driven watchdog will
> keep getting reset and prevent the watchdog from firing...
Yes....The alternative is finding all of the places in the kernel
where you would have to service the watchdog during the boot process.
Probably not many.....Depends upon the timeout value.
> ....... So, what's the likely hood of the boot process
> going bad?
My experience has been that unless the hardware is broken, it
tends to either work every time or fail every time.
> Our application requires downloading new kernels and applications and this
> increase the likely hood that a kernel fails to complete the boot process.
Yes, it will. But....what do you do after the new software
load fails to boot? It will just keep resetting and running the
same broken software......
> Maybe the timer can be set longer than the longest bootup time or at least
> until the first daemon gets going?
All of the timeout and other controls are in the write-once SYPCR.
Once you select the timeout and behavior, you have it until the
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
More information about the Linuxppc-embedded