From: Andre Schwarz <andre.schwarz@matrix-vision.de>
To: Scott Wood <scottwood@freescale.com>
Cc: linux-ppc list <linuxppc-dev@ozlabs.org>
Subject: Re: Question on MPC83xx interrupts
Date: Tue, 22 Apr 2008 20:51:23 +0200 [thread overview]
Message-ID: <480E33AB.5050904@matrix-vision.de> (raw)
In-Reply-To: <20080422174208.GB18076@ld0162-tx32.am.freescale.net>
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
Scott Wood schrieb:
> On Tue, Apr 22, 2008 at 07:36:48PM +0200, Andre Schwarz wrote:
>
>> thanks - any Idea how to figure out where the BAD comes from ?
>> Is it simply an unhandled/unacked one ?
>>
>
> It generally happens when an interrupt is requested, and the core takes
> the exception, but then the interrupt source deasserts itself.
>
> -Scott
> _______________________________________________
> Linuxppc-dev mailing list
> Linuxppc-dev@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-dev
>
So this is not bad at all if you have a device with self-clearing
interrupts ...
Thanks,
Andre
MATRIX VISION GmbH, Talstraße 16, DE-71570 Oppenweiler - Registergericht: Amtsgericht Stuttgart, HRB 271090
Geschäftsführer: Gerhard Thullner, Werner Armingeon, Uwe Furtner
[-- Attachment #2: Type: text/html, Size: 1391 bytes --]
next prev parent reply other threads:[~2008-04-22 18:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 16:58 Question on MPC83xx interrupts Andre Schwarz
2008-04-22 17:23 ` Scott Wood
2008-04-22 17:36 ` Andre Schwarz
2008-04-22 17:42 ` Scott Wood
2008-04-22 18:51 ` Andre Schwarz [this message]
2008-04-22 18:52 ` Scott Wood
2008-04-22 22:57 ` Michael Ellerman
2008-04-23 7:54 ` André Schwarz
2008-04-23 16:00 ` Segher Boessenkool
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=480E33AB.5050904@matrix-vision.de \
--to=andre.schwarz@matrix-vision.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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.