From: Dale Farnsworth <dale@farnsworth.org>
To: Stephen Horton <SHorton@kodiaknetworks.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: mpc744x, Marvell mv6446x kernel guidance please
Date: Wed, 30 Jul 2008 16:10:46 -0700 [thread overview]
Message-ID: <20080730231046.GA26011@farnsworth.org> (raw)
In-Reply-To: <295C5089A56CE143B316E5F67CA99CB001D06956@cowboy.inovate.inovate.com>
On Wed, Jul 30, 2008 at 08:56:18AM -0500, Stephen Horton wrote:
> Thanks for your kind encouragement. I now have a mostly booting kernel.
> I have just a few remaining issues to resolve; perhaps you (or others)
> can give me some tips regarding these:
>
> 1. In your prpmc2800 .dts configuration, in the PCI bus configuration
> section, you lay-out the IRQ mappings like this:
> interrupt-map = <
> /* IDSEL 0x0a */
> 5000 0 0 1 &/mv64x60/pic 50
> 5000 0 0 2 &/mv64x60/pic 51
> I've read the Open Firmware document on Interrupt Mapping, but I still
> don't really understand the first 3 columns (5000 0 0), especially where
> the first column comes from. Is this just some arbitrarily selected
> offset address for that device on the pci bus?
An address on the PCI bus is represented by 3 cells (96 bits).
Take a look at page 4 of http://www.openbios.org/data/docs/bus.pci.pdf
You'll see that the PCI device is contained in bits 15-11, selected by
the 0xf800 in interrupt-map-mask. The 0x5000 corresponds to device 0xa.
-Dale
next prev parent reply other threads:[~2008-07-30 23:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-11 3:46 mpc744x, Marvell mv6446x kernel guidance please Stephen Horton
2008-07-11 7:01 ` Marco Stornelli
2008-07-11 8:37 ` Welch, Martyn (GE EntSol, Intelligent Platforms)
2008-07-28 16:51 ` Mark A. Greer
2008-07-30 13:56 ` Stephen Horton
2008-07-30 23:10 ` Dale Farnsworth [this message]
2008-08-01 1:38 ` Stephen Horton
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=20080730231046.GA26011@farnsworth.org \
--to=dale@farnsworth.org \
--cc=SHorton@kodiaknetworks.com \
--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).