linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "John Nikiforos" <ppclinuxuser@yahoo.gr>
To: linuxppc-embedded@lists.linuxppc.org
Subject: MPC8260 + Interrupt 0
Date: Thu, 12 Sep 2002 06:09:11 +0100 (BST)	[thread overview]
Message-ID: <20020912050911.76262.qmail@web12905.mail.yahoo.com> (raw)


  As I can understand from the linux code,
interrupt value 0 is a valid value. But,
whats the expected number of such interrupts?
We sould expect 0,1 or 2, or does the processor
issue int 0 all the time? (when there is no
pending interrupt (MPC8260 Manual)).
In our system we count about 3000 BAD interrupts
every 10 seconds. Is it normal?

                            Thanks
                              John

=====
--/ /  (_)__  __ ____  __  / _ \/ _ \/ ___/
 / /__/ / _ \/ // /\ \/ / / /_ / /_ / /__
/____/_/_//_/\_,_/ /_/\_\/_/  /_/  /____/--


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

                 reply	other threads:[~2002-09-12  5:09 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20020912050911.76262.qmail@web12905.mail.yahoo.com \
    --to=ppclinuxuser@yahoo.gr \
    --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).