From: "ashish anand" <ashish_ibm@rediffmail.com>
To: linux-mips@linux-mips.org
Subject: does CP0_CAUSE gets set by spurious interrupts..?.
Date: 14 Nov 2003 08:46:06 -0000 [thread overview]
Message-ID: <20031114084606.23062.qmail@webmail29.rediffmail.com> (raw)
[-- Attachment #1: Type: text/html, Size: 418 bytes --]
[-- Attachment #2: Type: text/plain, Size: 147 bytes --]
Hello,
would a spurious interrupt ( edge vs. level trigger mismatching) cause CP0_CAUSE to show any pending interupts.?
Best Regards,
Ashish
next reply other threads:[~2003-11-14 8:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-14 8:46 ashish anand [this message]
2003-11-14 11:21 ` does CP0_CAUSE gets set by spurious interrupts..? Dominic Sweetman
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=20031114084606.23062.qmail@webmail29.rediffmail.com \
--to=ashish_ibm@rediffmail.com \
--cc=linux-mips@linux-mips.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