linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: xav <grave@ipno.in2p3.fr>
To: Gabriel Paubert <paubert@iram.es>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: How to find information for the Raven Chip ?
Date: Fri, 06 Apr 2001 08:26:45 +0200	[thread overview]
Message-ID: <3ACD61A4.F04B1AF3@ipno.in2p3.fr> (raw)
In-Reply-To: Pine.HPX.4.10.10103191008020.13151-100000@gra-ux1.iram.es


Gabriel Paubert wrote:

> On Mon, 12 Mar 2001, xav wrote:
>
> >
> > Hi,
> >
> > After I have followed the Matt's advice, I was able
> > to request irq for my tundra universe chip on my 2303
> > board (with 2.4.2 kernel from bk tree). But when I enable vme
> > irq 6 on it : it seems that this irq is always on (no problem with
> > others vme irq). Where can I look for the
> > information about level/edge in the Raven chip ?
>
> If the problem is only with one of the VME irqs, it is likely a stuck IRQ
> line on the vme bus or a faulty interface on the MVME board. All
> enabled VME irq trigger the same PCI irq (LIRQ0 on the PCI side).
>
> Either this or you have a RORA interrupt that you don't clear properly.
>
>         Regards,
>         Gabriel.

Hi !

The problem was an hardware one...
I just move the mvme2301 board from slot 0 to 2 and now everything works
fine : interrupt, A16/A24 and A32 reads and writes.

Thanks for the help...

O+ xavier


--
33 (0) 1 69 15 79 59
De chacun selon ses forces, a chacun selon ses besoins


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

      reply	other threads:[~2001-04-06  6:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-12  9:02 How to find information for the Raven Chip ? xav
2001-03-12 17:22 ` Mark A. Greer
2001-03-19  9:10 ` Gabriel Paubert
2001-04-06  6:26   ` xav [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=3ACD61A4.F04B1AF3@ipno.in2p3.fr \
    --to=grave@ipno.in2p3.fr \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=paubert@iram.es \
    /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).