Dear Eric Nelson, In message <4fcd17a5.6030...@boundarydevices.com> you wrote: > > > The function of the watchdog should be reserved for auch systems who > > need it to implement security related functions; messing with it in > > unrelated places (like setting it into unexpected states and or > > timeouts) may cause undefined behaviour on such systems. > > > > Don't do it. > > > > My comment is that reset_cpu() should probably not return, and > at the moment it will. The minimum WDT timeout value is 1/2 second, so > execution will continue for some time less than that. > > It seems to me that this might be a bad thing, allowing unexpected > execution of commands in a script after the execution of the 'reset' > command. > > If I understand your comment, you're saying that reset_cpu() should > not be implemented using the watchdog. > > Is that right?
No, that was not my intention. I must have missed the fact that you were talking about reset_cpu() and only this function. Please ignore me. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: w...@denx.de "In Christianity neither morality nor religion come into contact with reality at any point." - Friedrich Nietzsche _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
