From: Dan Malek <dmalek@jlc.net>
To: Graham Stoney <greyham@research.canon.com.au>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: /dev/watchdog for onchip MPC860 watchdog?
Date: Mon, 18 Oct 1999 16:24:59 -0400 [thread overview]
Message-ID: <380B821B.F1C79A32@jlc.net> (raw)
In-Reply-To: 19991015033031.18664848C@elph.research.canon.com.au
Graham Stoney wrote:
>
> Dear Embeddees,
>
> I'm wondering if anyone is working on a driver to provide the /dev/watchdog
> interface to the MPC860's on-chip watchdog?
The difficulty with the on-chip watchdog isn't the driver but
the coordination with the boot roms. The "auto-reset" features
of the 8xx (watch dog, bus monitor, etc.) are part of a write once
configuration register. Once disabled, they can't be enabled
again until the processor is reset.
If the boot rom enables these features (especially the watch dog),
you must service this as part of the Linux kernel processing. You
can't wait around for some application at a later time to determine
it now wants to enable and process the watchdog.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~1999-10-18 20:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-15 3:30 /dev/watchdog for onchip MPC860 watchdog? Graham Stoney
1999-10-18 20:24 ` Dan Malek [this message]
[not found] <380B6A1B.E5D02094@netx4.com>
1999-10-19 8:56 ` Graham Stoney
1999-10-19 19:51 ` Dan Malek
1999-10-20 1:56 ` Jeff Millar
1999-10-20 17:47 ` Dan Malek
1999-10-21 3:49 ` Graham Stoney
1999-10-21 4:06 ` Cort Dougan
-- strict thread matches above, loose matches on Subject: below --
1999-10-20 7:33 Raphael Massin
1999-10-20 17:56 ` Dan Malek
2000-07-13 7:24 Tania Boak
2000-07-13 7:47 ` Graham Stoney
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=380B821B.F1C79A32@jlc.net \
--to=dmalek@jlc.net \
--cc=greyham@research.canon.com.au \
--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).