All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Tim Moloney" <moloney@mrsl.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: Interrupt handling via OpenPIC
Date: Wed, 11 Apr 2001 13:24:57 -0400	[thread overview]
Message-ID: <00bf01c0c2ac$54b6e650$6c125acf@mrsl.com> (raw)


I am writing a device driver for a custom PMC card, and I'm having
trouble with the interrupt service routine.

Although the PCI configuration block says that the board's interrupt
is 9, I am receiving interrupt 3.  I know that the OpenPIC is supposed
to remap the interrupts but I don't quite understand the process.
I've looked at the board's users manual and skimmed the Linux kernel
but I can't find a good example of what to do.

Can anyone provide pointers to documentation, example code, etc. that
shows how I can reconcile what the kernel thinks the interrupt is with
what in actually being generated?

Additional info:
I am developing on a Synergy Microsystems VSS4 board.  This is a
quad-G4 VME board that has the following:
  IBM MPIC-2 interrupt controller
  Motorola MPC106 Grackle PCI bridge/memory controller
  Symbios 53c885 Ethernet/SCSI controller
  Tundra Universe II PCI-VME64 bridge
  DEC/Intel 21554 PCI-PCI bridge

Thanks for any help.

Tim Moloney

ManTech Real-time Systems Laboratory
2015 Cattlemen Road
Sarasota, FL  34232
(941) 377-6775 x208


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

             reply	other threads:[~2001-04-11 17:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-11 17:24 Tim Moloney [this message]
2001-04-11 19:56 ` Interrupt handling via OpenPIC Cort Dougan
2001-04-11 23:48   ` Tim Moloney
  -- strict thread matches above, loose matches on Subject: below --
2001-04-11 17:00 Tim Moloney

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='00bf01c0c2ac$54b6e650$6c125acf@mrsl.com' \
    --to=moloney@mrsl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.