From: Dan Malek <dan@embeddededge.com>
To: dnevil@snmc.com
Cc: linuxppc-embedded@lists.linuxppc.org, sjl@dent.vctlabs.com
Subject: Re: No Input from SMC1 on MPC860T - Resolved
Date: Wed, 22 May 2002 23:31:08 -0400 [thread overview]
Message-ID: <3CEC627C.9000709@embeddededge.com> (raw)
In-Reply-To: 1541.206.104.177.96.1022091123.squirrel@nevil.org
Daris A Nevil wrote:
>>The key was to not enable the FRZ signal when setting up the timerbase;
>>apparently I was getting a spurious freeze signal which was turning off
>>my timer interrupts partway through.
If you are getting a "spurious freeze" signal, wouldn't you consider
something amiss with your hardware design or SIU/debug configuration?
If the timers are responding to a freeze condition, so is the rest
of the processor core, which isn't a good thing unless you are actively
debugging.
Please do not apply this patch, but rather find the cause of the real
problem since I prefer to freeze the timers while debugging.
-- Dan
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-05-23 3:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 18:12 No Input from SMC1 on MPC860T - Resolved Daris A Nevil
2002-05-23 3:31 ` Dan Malek [this message]
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=3CEC627C.9000709@embeddededge.com \
--to=dan@embeddededge.com \
--cc=dnevil@snmc.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=sjl@dent.vctlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.