From: fche@redhat.com
To: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Hardware Watchdog
Date: Thu, 26 Jul 2001 04:58:00 -0000 [thread overview]
Message-ID: <200107261156.f6QBusX14487@touchme.toronto.redhat.com> (raw)
In-Reply-To: <20010726125313.A14929@frequentis.com>
Content-Type: text/plain; charset=US-ASCII
From: fche@redhat.com (Frank Ch. Eigler)
Date: 26 Jul 2001 07:56:53 -0400
In-Reply-To: < 20010726125313.A14929@frequentis.com >
Message-ID: <o5ofq7ucmy.fsf@touchme.toronto.redhat.com>
Lines: 23
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley)
MIME-Version: 1.0
Christoph Csebits <christoph.csebits@frequentis.com> writes:
: [...]
: im having a MPC860T based board with
: an hardware watchdog on it.
: [...]
: In eCos applications i am having a
: separate thread triggering the watchdog.
: No problem.
: [...]
: What do you think about using some
: of the timer interrupts for generating
: the watchdog triggers.
Is it typical to put watchdog reset calls into separate dedicated
threads, or low-level automatically-invoked code like interrupt
handlers? I was under the impression that watchdog resets are most
appropriately placed within the activity loops of the application code
itself -- it is their demise that the watchdog mechanism is meant to
detect.
- FChE
next prev parent reply other threads:[~2001-07-26 4:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-26 3:55 Christoph Csebits
2001-07-26 4:58 ` fche [this message]
2001-07-26 7:27 Doug Fraser
2001-07-26 7:51 ` Christoph Csebits
2001-07-26 8:50 ` Gary Thomas
2001-07-26 9:20 ` Christoph Csebits
2001-07-26 9:25 ` Gary Thomas
2001-07-26 11:30 ` Robin Farine
2001-07-26 23:26 ` Christoph Csebits
2001-07-26 23:57 ` Robin Farine
2001-07-27 1:28 ` Christoph Csebits
2001-07-27 1:50 ` Robin Farine
2001-07-26 10:02 Doug Fraser
2001-07-26 10:13 ` Gary Thomas
2001-07-26 13:21 Doug Fraser
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200107261156.f6QBusX14487@touchme.toronto.redhat.com \
--to=fche@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).