linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Robin Gilks <robin.gilks@tait.co.nz>
To: Wolfgang Denk <wd@denx.de>,
	linuxppc mail list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: PATCH: Another mpc8xx watchdog driver !!
Date: Wed, 07 Jan 2004 13:03:16 +1300	[thread overview]
Message-ID: <3FFB4CC4.5000606@tait.co.nz> (raw)
In-Reply-To: <20040106233539.63641C12DD@atlas.denx.de>


Wolfgang Denk wrote:
> In message <3FFB450D.7060405@tait.co.nz> you wrote:
>
>>>Do you really mean RTC here???
>>
>>Yes - the 866 and derivatives (859 etc) do NOT have a Real Time Clock
>>block. This means that hooking the RTC interrupt to 'kick the dog' is
>>rather difficult :-))
>
>
> That may be the case. But the watchdog code does not use any  RTC  at
> all.
>
>
>>"It is based on the code of Florian Schirmer but using kernel timers (as
>>used by the DENX driver) rather than the RTC."
>
>
> Have you ever seen a MPC8xx watchdog driver that used RTC for
> triggering?

Gosh - egg on face. Got mixed up with the PIT which usually uses a 32KHz
crystal as does the RTC on the mpc860. Well, we don't have a crystal on
the PIT so that (as well as the non-existant RTC) is not available!!

This is what comes from trying to rely on memory alone with 1358 pages
of mpc866 manual :-))

--
Robin Gilks
Senior Design Engineer          Phone: (+64)(3) 357 1569
Tait Electronics                Fax  :  (+64)(3) 359 4632
PO Box 1645 Christchurch        Email : robin.gilks@tait.co.nz
New Zealand


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

  reply	other threads:[~2004-01-07  0:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3FFB450D.7060405@tait.co.nz>
2004-01-06 23:35 ` PATCH: Another mpc8xx watchdog driver !! Wolfgang Denk
2004-01-07  0:03   ` Robin Gilks [this message]
2004-01-07  0:11   ` Dan Malek
2004-01-06 22:28 Robin Gilks
2004-01-06 23:06 ` 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=3FFB4CC4.5000606@tait.co.nz \
    --to=robin.gilks@tait.co.nz \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=wd@denx.de \
    /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).