From: Hollis Blanchard <hollis@austin.ibm.com>
To: Anders Blomdell <anders.blomdell@control.lth.se>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Problems with 2_4_devel & MVME2600 serial interrupts
Date: 18 Oct 2002 10:15:35 -0500 [thread overview]
Message-ID: <1034954142.8169.91.camel@granite.austin.ibm.com> (raw)
In-Reply-To: <432E39D0-E2AA-11D6-8132-0003931C2BFA@control.lth.se>
On Fri, 2002-10-18 at 09:59, Anders Blomdell wrote:
>
> > 2. When the interrupts gets enabled, the system gets an interrupt and
> > eventually
> > calls i8259_irq, which reads 0xff from pci_intack, which it will
> > continue to
> > do forever in this loop (do_IRQ, arch/kernel/irq.c):
>
> A quick (and working, but probably unclean) solution is call
> 'i8259_init(intack_addr)' with intack_addr set to zero (instead of the
> 0xbffffff0 from prep_setup.c), thus forcing the interrupt to be polled from
> the 8259 controller. Could somebody who understands open_pic (is this a
> relative to MPIC?), give me a hint of suitable further reading before I to
> try to clean this up?
Seems to me that either:
a) the pci_intack value is incorrect for your board, in which case you
should correct it
b) your board's int-ack feature is broken and you'll need to poll
-Hollis
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-10-18 15:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-17 14:52 Problems with 2_4_devel & MVME2600 serial interrupts Anders Blomdell
2002-10-18 14:59 ` Anders Blomdell
2002-10-18 15:15 ` Hollis Blanchard [this message]
2002-10-18 15:47 ` Anders Blomdell
2002-10-18 16:04 ` Hollis Blanchard
2002-10-18 19:33 ` Hollis Blanchard
2002-10-18 20:03 ` Tom Rini
2002-10-19 18:35 ` Anders Blomdell
2002-10-19 19:14 ` 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=1034954142.8169.91.camel@granite.austin.ibm.com \
--to=hollis@austin.ibm.com \
--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).