linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: linuxppc-embedded@ozlabs.org
Subject: Re: 440SP External Interrupt IRQ
Date: Fri, 6 Oct 2006 06:46:22 +0200	[thread overview]
Message-ID: <200610060646.23125.sr@denx.de> (raw)
In-Reply-To: <20061006034949.17839.qmail@web33407.mail.mud.yahoo.com>

Jeff,

On Friday 06 October 2006 05:49, Jeff Stevens wrote:
> I am trying to figure out the PCI IRQ mapping on a
> 440SP processor in linux-2.6.17.9.  I have a board
> that is based off of the Luan development board, and I
> am not sure which IRQ corresponds to each external
> IRQ[0:5] pins on the processor.  Where can I find this
> information?

In your schematics. Sorry but it's that simple.

Best regards,
Stefan

  reply	other threads:[~2006-10-06  4:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06  3:49 440SP External Interrupt IRQ Jeff Stevens
2006-10-06  4:46 ` Stefan Roese [this message]
2006-10-06 10:27   ` Jeff Stevens
2006-10-06 16:06     ` Eugene Surovegin

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=200610060646.23125.sr@denx.de \
    --to=sr@denx.de \
    --cc=linuxppc-embedded@ozlabs.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).