Carl-Daniel Hailfinger wrote:
Hi Joe,
your quoting seems to be messed up somehow.
On 16.04.2008 17:21, joe@settoplinux.org wrote:
On Tue, 2008-04-08 at 01:13 +0200, Peter Stuge wrote:
True, but it's not very easy to regularly poke the timer without an interrupt - or the code will be full of try_poke() every other line.
What about the mostly existing code that pokes port 0x80? make it a macro that also pokes the WDT?
If there are "long" sections for a single POST code, (like clearing 4GB ECC ram), having a bit toggling would be less boring to watch anyhow.
Please avoid any POST code toggling. There are POST boards out there which display the last n POST codes and make it a lot easier to follow the code path. Once you add POST code toggling, that history is flushed away really fast.
Full ack. In addition, showing post codes and triggering a watchdog are two fundamentally different things. I think we should not let the one implicitly do the other.
Stefan