From: "McMullan, Jason" <jason.mcmullan@timesys.com>
To: <vbordug@mvista.com>
Cc: PPC_LINUX <linuxppc-embedded@ozlabs.org>
Subject: PQ2FADS PCI Interrupts
Date: Fri, 24 Jun 2005 11:33:09 -0400
Date: Fri, 24 Jun 2005 11:25:18 -0400 [thread overview]
Message-ID: <1119627190.28058.39.camel@jmcmullan.timesys> (raw)
[-- Attachment #1: Type: text/plain, Size: 622 bytes --]
(This is mainly for Vitaly B., but others may be interested)
Given your latest MPC82xx PCI patches to the list, PCI support
is *better*, but interrupts are *not* delivered on the PQ2FADS
One question I have, is that it seems that on the MPC8280, at
least, the PCI interrupt vector is 0x12, not the SIU_INT6
vectors, according to MPC8280RM.pdf, Table 4-3 on page 4-16.
Vitaly, where are places in your PCI patch where you were
uncertain of board differences between the PQ2FADS and the
MPC8272ADS, so that I can verify those first?
--
Jason McMullan <jason.mcmullan@timesys.com>
TimeSys Corporation
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-06-24 15:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 15:33 McMullan, Jason [this message]
2005-06-24 19:20 ` PQ2FADS PCI Interrupts Jason McMullan
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=1119627190.28058.39.camel@jmcmullan.timesys \
--to=jason.mcmullan@timesys.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=vbordug@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