linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Stefano Coluccini" <s.coluccini@caen.it>
To: "Matt Porter" <mporter@mvista.com>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: RE: Bogus interrupt
Date: Wed, 28 Feb 2001 09:29:18 +0100	[thread overview]
Message-ID: <NDBBIFIMCKPOADMAJOKMGEIFCPAA.s.coluccini@caen.it> (raw)
In-Reply-To: <20010227051445.A32137@cx258813-a.chnd1.az.home.com>


> > Hi everyone,
> >   I'm trying to run kernel 2.5 on Motorola MVME5100 and, after the sti
> > istruction in start_kernel, the kernel hangs due to a spurious
> interrupt.
> > (Bogus interrupt -1)
> > Is this a well-known problem also in other ports ? or have
> anyone of you a
> > suggestion to solve this ?
>
> If you are using the default openpic initsenses in prep_pci.c then you
> might see this problem since MPIC input 1 now has the 550 UART.  You'll
> need to change the initsenses since the edge triggered ECC interrupt
> used to be on input 1 on the older boards.
>
I've started working on MCPN765 port, since I think MVME5100 is an MCPN765
with a VME Bridge and without an ISA bridge, so I think the senses of
interrupt are correct because the 5100 and the 765 manual page related to
the interrupt senses is exactly the same (or it is a cut&paste error ??? :))
However this problem, like many other I've encountered, are all due to a bad
cross-compiler :(. I start working today with a good environment after a
month of nightmares !

Thank you very much for the help.
Stefano.


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

  reply	other threads:[~2001-02-28  8:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-26 11:54 Bogus interrupt Stefano Coluccini
2001-02-27 12:14 ` Matt Porter
2001-02-28  8:29   ` Stefano Coluccini [this message]
2001-03-01  0:12     ` Matt Porter
2001-03-01  9:55       ` Bogus interrupt + little Makefile bug Stefano Coluccini
2001-03-01 15:17         ` MVME5100 was " Matt Porter
2001-03-02  3:43           ` 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=NDBBIFIMCKPOADMAJOKMGEIFCPAA.s.coluccini@caen.it \
    --to=s.coluccini@caen.it \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=mporter@mvista.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;
as well as URLs for NNTP newsgroup(s).