From: david.hagood@gmail.com
To: "Chen, Tiejun" <Tiejun.Chen@windriver.com>
Cc: linuxppc-dev@ozlabs.org, David Hagood <david.hagood@gmail.com>
Subject: RE: MPC8641D PEX: programming OWBAR in Endpoint mode?
Date: Thu, 23 Sep 2010 09:44:09 -0500 [thread overview]
Message-ID: <409c3f6d508ece73c18f6ce750513b22.squirrel@localhost> (raw)
In-Reply-To: <52CF90264091A14888078A031D780F4306C8C14B@ism-mail03.corp.ad.wrs.com>
>> -----Original Message-----
via the BARs.
>
> I read your email again and something hint me. I notice you clarify you
> already condigure InBound successfully.
I am programming BOTH the inbound ATMUs to make PPC memory available to
the root complex, AND programming outbound ATMUs to enable the PPC to bus
master to the root complex's memory space on PCIe.
I am NOT attempting to program the IWBARs - as you noted, they get
programmed by the root complex via PCI config operations.
>
> And as my above comment I'm afraid you
> mix up InBound and OutBound on EP mode?
No, I am NOT confusing the two - that is why I am being VERY EXPLICIT
about accessing the OUTBOUND ATMUs.
The only reason I mention the inbound ATMUs is to demonstrate that the
physical layer is working.
next prev parent reply other threads:[~2010-09-23 14:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 15:55 MPC8641D PEX: programming OWBAR in Endpoint mode? david.hagood
2010-09-23 3:21 ` Chen, Tiejun
2010-09-23 11:11 ` David Hagood
2010-09-23 14:10 ` Chen, Tiejun
2010-09-23 14:44 ` david.hagood [this message]
2010-09-24 5:09 ` Chen, Tiejun
2010-09-24 10:50 ` David Hagood
2010-09-25 9:46 ` tiejun.chen
2010-09-25 11:51 ` David Hagood
2010-09-26 10:14 ` tiejun.chen
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=409c3f6d508ece73c18f6ce750513b22.squirrel@localhost \
--to=david.hagood@gmail.com \
--cc=Tiejun.Chen@windriver.com \
--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).