linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: "Banks, Kelly" <kelly.banks@gilbarco.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: MPC860 onchip WatchDog
Date: Wed, 06 Mar 2002 23:22:22 +0100	[thread overview]
Message-ID: <20020306222227.84168109EB@denx.denx.de> (raw)
In-Reply-To: Your message of "Wed, 06 Mar 2002 17:01:30 EST." <A3E34B558F5CD211B4980008C7A4A9900242418D@sparrow.gso.mcs.marconi.com>


In message <A3E34B558F5CD211B4980008C7A4A9900242418D@sparrow.gso.mcs.marconi.com> you wrote:
>
> I just did this last week.  My test load is cooking in the test oven now.
> You need to tickle the WD at several places within the kernel.  For me, it

Depends on what you want to do. Normally it's sufficient to make sure
one top-level application process is  running,  so  a  normal  device
driver  is sufficient - see for instance drivers/char/wdt_mpc8xx.c in
our kernel source tree.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
There are two ways of constructing a software design. One way  is  to
make  it  so  simple that there are obviously no deficiencies and the
other is to make it so complicated that there are  no  obvious  defi-
ciencies.                             - Charles Anthony Richard Hoare

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2002-03-06 22:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-06 22:01 MPC860 onchip WatchDog Banks, Kelly
2002-03-06 22:22 ` Wolfgang Denk [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-06 23:56 Andres Chamorro Morillas
2002-03-06 22:19 ` Wolfgang Denk

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=20020306222227.84168109EB@denx.denx.de \
    --to=wd@denx.de \
    --cc=kelly.banks@gilbarco.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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 NNTP newsgroup(s).