linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Khai Trinh <kqtrinh@yahoo.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: 440 PCI adapter card interupt handling question
Date: Thu, 13 Jun 2002 15:10:11 -0700 (PDT)	[thread overview]
Message-ID: <20020613221011.85904.qmail@web11502.mail.yahoo.com> (raw)


Our custom board is a IBM 440GP based pci slave
adapter card, we will configure it to use the Simple
Message Passing Unit to allow interrupt generation to
the 440 from the Host. My question are Where in the
Linux kernel code can I initialize the 440 onboard
interrupt controller to enable this interrupt to
happen? And how do I register my interrupt handling
routine to service inbound interrupt from the Host?

Regards,
--Khai


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

             reply	other threads:[~2002-06-13 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-13 22:10 Khai Trinh [this message]
2002-06-15 15:21 ` 440 PCI adapter card interupt handling question Matt Porter
2002-06-17 17:32   ` Khai Trinh
2002-06-17 17:58     ` Matt Porter

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=20020613221011.85904.qmail@web11502.mail.yahoo.com \
    --to=kqtrinh@yahoo.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).