linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "tiejun.chen" <tiejun.chen@windriver.com>
To: David Hagood <david.hagood@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: MPC8641D PEX: programming OWBAR in Endpoint mode?
Date: Sat, 25 Sep 2010 17:46:56 +0800	[thread overview]
Message-ID: <4C9DC510.8010403@windriver.com> (raw)
In-Reply-To: <1285325425.2454.11.camel@chumley>

David Hagood wrote:
> On Fri, 2010-09-24 at 07:09 +0200, Chen, Tiejun wrote:
> 
>> Right but this should be done for RC mode, not for EP mode we're
>> discussing.
>>
>> Tiejun
> 
> According to the Freescale documentation, outbound is just as valid for
> endpoint as for root complex - indeed, to generate MSIs from software

Yes.

As a summary you have no any issue to access InBound/BAR/LAW. And actually I'm
always strange that even you cannot configure InBound/BAR/LAW properly, you also
should be allowed to write OutBound REGs. And I remember there is only one
requirement to OutBound, and that is the window address should be aligned based
on the size from OWS. Are you sure?

And did you try to configure OutBound REGS when RC mode? If so I'm afraid we may
miss some errata on EP.

And do you have any response from Freescale?

Cheers
Tiejun

> REQUIRES programming an outbound ATMU to access the host's APIC.
> 
> Moreover, ANY PCI endpoint SHOULD be able to do bus master access, and
> that is done by the outbound ATMUs.
> 
> 
> 

  reply	other threads:[~2010-09-25  9:45 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
2010-09-24  5:09         ` Chen, Tiejun
2010-09-24 10:50           ` David Hagood
2010-09-25  9:46             ` tiejun.chen [this message]
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=4C9DC510.8010403@windriver.com \
    --to=tiejun.chen@windriver.com \
    --cc=david.hagood@gmail.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).