From: James Chapman <jchapman@katalix.com>
To: "Mark A. Greer" <mgreer@mvista.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH 2.6.11-rc4] ppc: add support for Radstone ppc7d boards
Date: Mon, 28 Feb 2005 22:13:16 +0000 [thread overview]
Message-ID: <4223977C.4070502@katalix.com> (raw)
In-Reply-To: <422384CA.6090004@mvista.com>
Mark A. Greer wrote:
> > + /* Setup P2P for PCI#0 */
> > + val32 = mv64x60_read(&bh, MV64x60_PCI0_P2P_CONFIG);
> > + val32 &= ~(0x00ffffff);
> > + val32 |= ((bh.hose_a->first_busno & 0xff) << 16);
> etc.
>
> Do you really use the P2P bridge? Unless I missed something, I think it
> remains disabled. You shouldn't need it unless you have PCI devices on
> one hose directly accessing PCI devices on the other hose. The P2P
> stuff seems complicated & unnecessary.
Thinking about this more, what is really being configured here is the
primary bus number before the scan is performed. If the bus number
doesn't match the hose's primary bus number, the mv64x60 will issue
Type 2 PCI config cycles instead of Type 1 and the scan will fail.
This board has an on-board PCI-X bridge and potentially other PCI
bridges on PMC cards. I found that I had to init the P2P_CONFIG
primary bus value before scan in order for the PCI scan of bus 2
to work (hose_a has PCI busses 0 and 1).
I think the writes to the P2P config registers are necessary.
/james
--
James Chapman
PGP key : http://www.katalix.com/~jchapman/pgpkey.txt
next prev parent reply other threads:[~2005-02-28 22:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-28 17:55 [PATCH 2.6.11-rc4] ppc: add support for Radstone ppc7d boards James Chapman
2005-02-28 20:53 ` Mark A. Greer
2005-02-28 21:31 ` James Chapman
2005-02-28 22:13 ` James Chapman [this message]
2005-02-28 22:24 ` Mark A. Greer
2005-03-01 19:29 ` James Chapman
2005-03-03 17:58 ` Mark A. Greer
2005-03-03 22:06 ` [PATCH 2.6.11-rc5] ppc32: add Radstone PPC7D platform support James Chapman
2005-03-03 22:50 ` James Chapman
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=4223977C.4070502@katalix.com \
--to=jchapman@katalix.com \
--cc=linuxppc-embedded@ozlabs.org \
--cc=mgreer@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.