From: "David Adair" <dadair@ariodata.com>
To: "'Praveen Mehrotra'" <praveen.mehrotra@gmail.com>,
<linuxppc-embedded@ozlabs.org>
Subject: RE: Critical Interrupt on 405EP
Date: Wed, 3 Nov 2004 20:48:00 -0800 [thread overview]
Message-ID: <ORIONuNjVuMhvqgStMV000000ab@orion.ariodata.com> (raw)
In-Reply-To: <a2ea557e041103180817107b9e@mail.gmail.com>
You might want to check out the old e-mails about CI on the 440.
I use 2.4.19 + some cruft on a 440GP. In this case
SPRN_SPRG0 and SPRN_SPRG1 are used by both critical and non-critical
interrupts making it just a matter of time before the CI stomps
on a normal interrupt. You can look at the "PROLOG" stuff in
the appropriate head_xxx.S file to see if you have the same issue.
Have not actually run it, but looking at the code 2.6 is much
closer although. I don't yet understand why crit_transfer_to_handler,
ret_from_crit_exc were not used here though:
#define CRITICAL_EXCEPTION(n, label, hdlr) \
START_EXCEPTION(label); \
CRITICAL_EXCEPTION_PROLOG; \
addi r3,r1,STACK_FRAME_OVERHEAD; \
EXC_XFER_TEMPLATE(hdlr, n+2, (MSR_KERNEL & ~(MSR_ME|MSR_DE|MSR_CE)),
\
NOCOPY, transfer_to_handler_full, \
ret_from_except_full)
David
> -----Original Message-----
> From: linuxppc-embedded-bounces@ozlabs.org [mailto:linuxppc-embedded-
> bounces@ozlabs.org] On Behalf Of Praveen Mehrotra
> Sent: Wednesday, November 03, 2004 6:09 PM
> To: linuxppc-embedded@ozlabs.org
> Subject: Critical Interrupt on 405EP
>
> Hello,
>
> I'm running 2.4.20 kernel on a 405EP board and am interested in using
> critical interrupt for one of the devices. I've almost got it working,
> except that after several minutes (ranging from 10-30) of operation
> kernel crash occurs.
>
> Has anyone got the critical interrupt on 405EP working for 2.4.x
> kernels ? I can post details specific to changes I made if someone has
> experience regarding this.
>
> Thanks,
> Praveen
> _______________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
prev parent reply other threads:[~2004-11-04 4:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-04 2:08 Critical Interrupt on 405EP Praveen Mehrotra
2004-11-04 4:48 ` David Adair [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=ORIONuNjVuMhvqgStMV000000ab@orion.ariodata.com \
--to=dadair@ariodata.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=praveen.mehrotra@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox