From: Zang Roy-r61911 <tie-fei.zang@freescale.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
"Alexandre.Bounine@tundra.com" <Alexandre.Bounine@tundra.com>
Subject: Re: MPC7448_HPC2 question
Date: 25 Oct 2006 17:31:29 +0800 [thread overview]
Message-ID: <1161768688.17597.8.camel@localhost.localdomain> (raw)
In-Reply-To: <1161753605.22582.42.camel@localhost.localdomain>
On Wed, 2006-10-25 at 13:20, Benjamin Herrenschmidt wrote:
>
> Cannot be replaced by:
>
> pci_read_irq_line(dev);
When I use pci_read_irq_line(), the pci interrupt number exceeds the
limit of mpic-> irq_count. my mpic->irq_count = 0x18, which is gotten
from on chip register.
mpic_host_map() can not return successful value.
Roy
next prev parent reply other threads:[~2006-10-25 9:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 5:20 MPC7448_HPC2 question Benjamin Herrenschmidt
2006-10-25 5:31 ` Zang Roy-r61911
2006-10-25 9:31 ` Zang Roy-r61911 [this message]
2006-10-25 13:45 ` Benjamin Herrenschmidt
2006-10-26 7:59 ` Zang Roy-r61911
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=1161768688.17597.8.camel@localhost.localdomain \
--to=tie-fei.zang@freescale.com \
--cc=Alexandre.Bounine@tundra.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@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).