From: Tom Rini <trini@kernel.crashing.org>
To: Anders Blomdell <anders.blomdell@control.lth.se>
Cc: linuxppc embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: PrPMC800 interrupt problem
Date: Fri, 25 Oct 2002 08:40:20 -0700 [thread overview]
Message-ID: <20021025154020.GA30713@opus.bloom.county> (raw)
In-Reply-To: <A347A662-E82C-11D6-A4F1-0003931C2BFA@control.lth.se>
On Fri, Oct 25, 2002 at 05:15:46PM +0200, Anders Blomdell wrote:
> The problem seems to be that the UART generates an Harrier internal
> interrupt. This should be handled as any other MPIC interrupt, but it isn'
> t. This lack of an appropriate handler (irq_desc[16].handler == 0) makes
> the Harrier chip wait forever for an EOI.
>
> A very hacky solution to this is to modify 'prpmc800_init_IRQ' to:
Did you update the initsenses table as well? And are you sure you are
calling openpic_set_sources() correctly? That only maps OpenPIC source
16 to be Linux interrupt 16, and doesn't catch any of the other sources
('tho I don't have the prpmc800 manual in front of me)
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-10-25 15:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 17:01 PrPMC800 interrupt problem Anders Blomdell
2002-10-24 17:26 ` Tom Rini
2002-10-25 15:15 ` Anders Blomdell
2002-10-25 15:40 ` Tom Rini [this message]
2002-10-25 15:50 ` Anders Blomdell
2002-10-25 16:04 ` Tom Rini
2002-10-25 16:51 ` Matt Porter
2002-10-25 15:44 ` Anders Blomdell
2002-10-25 16:00 ` Tom Rini
2002-10-25 16:42 ` Anders Blomdell
2002-10-26 1:39 ` Tom Rini
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=20021025154020.GA30713@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=anders.blomdell@control.lth.se \
--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).