linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: Anders Blomdell <anders.blomdell@control.lth.se>
Cc: Hollis Blanchard <hollis@austin.ibm.com>,
	linuxppc embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Problems with 2_4_devel & MVME2600 serial interrupts
Date: Sat, 19 Oct 2002 12:14:24 -0700	[thread overview]
Message-ID: <20021019191424.GB722@opus.bloom.county> (raw)
In-Reply-To: <1035052555.1506.10.camel@maj.hemma>


On Sat, Oct 19, 2002 at 08:35:52PM +0200, Anders Blomdell wrote:
> > On Fri, Oct 18, 2002 at 05:47:32PM +0200, Anders Blomdell wrote:
> > >
> > > >Seems to me that either:
> > > >a) the pci_intack value is incorrect for your board, in which case you
> > > >should correct it
> > > Shure is, question is if it really should be caught from the pci_intack
> > > register, as far as I can understand from the MVME2600 doc's, the 8259
> > > interrupt generates a MPIC-IRQ0, but one has to poll the 8259 to find out
> > > what device it was that generated the interrupt.
> >
> > Are you running this as CONFIG_ALL_PPC?  IIRC, under 2_4_devel, this
> > board should work as CONFIG_PPLUS.  Or it will need minor fixups, which
> > I have described previously on the lists (and possibly to you as well)
> > for the OpenPIC table.
> CONFIG_ALL_PPC, yes.
> >
> > > >b) your board's int-ack feature is broken and you'll need to poll
> > >
> > > Perhaps an extra field in the 'mot_info' (arch/ppc/platforms/prep_pci.c) is
> > > called for? This line in prep_init_IRQ (arch/ppc/platforms/prep_setup.c):
> > >
> > >   i8259_init(0xbffffff0); /* PCI interrupt ack address for MPC105 and 106
> > > */
> > >
> > > does not look like a general solution.
> >
> > Well, it's a correct solution for the PReP like PReP machines.  Where in
> > the continium does the MVME2600 fall exactly?
> > MPC105/MPC106/Raven/Hawk/Falcon ?  I _think_ this is an example of why
> > it would really be nice to kill PPLUS support from PReP.  But I know
> > that will upset some people, so I'm not advocating that for 2.4, and it
> > looks like we might have to do something similar to the MPC10x test in
> > the PReP bootwrapper code in 2.5 (and maybe 2.4? I'm not at home, so I
> > can't easily check).
> It's a Raven equipped card, and as far as I can find, the 8259
> interrupts acks are not accessible from any other adress. I'll look
> further into this on monday...

Any address other than what?  If i8259_init is passed 0, then we poll,
instead of asking the int-ack.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2002-10-19 19:14 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
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 [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=20021019191424.GB722@opus.bloom.county \
    --to=trini@kernel.crashing.org \
    --cc=anders.blomdell@control.lth.se \
    --cc=hollis@austin.ibm.com \
    --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).