From: David Hagood <david.hagood@gmail.com>
To: "tiejun.chen" <tiejun.chen@windriver.com>
Cc: Scott Wood <scottwood@freescale.com>,
linuxppc-dev@lists.ozlabs.org,
"Ira W. Snyder" <iws@ovro.caltech.edu>
Subject: Re: Parsing a bus fault message?
Date: Fri, 08 Oct 2010 06:16:12 -0500 [thread overview]
Message-ID: <1286536572.2545.16.camel@chumley> (raw)
In-Reply-To: <4CAEE2EC.2020103@windriver.com>
On Fri, 2010-10-08 at 17:22 +0800, tiejun.chen wrote:
>
> I think it should be allowed to use two LAWs to map different space for PCIe
> since I ever saw more one LAWs are created for different RAM space.
>
> Sorry for this delay response.
>
> -Tiejun
It's my bad, as I'd worked out the problem: the host root complex had to
be forced to rescan the device and enable bus mastering on that side of
things. Once that happened, I could access PCI space.
I should have posted my success.
prev parent reply other threads:[~2010-10-08 11:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-28 14:26 Parsing a bus fault message? david.hagood
2010-09-28 15:31 ` Ira W. Snyder
2010-09-28 18:45 ` Scott Wood
2010-09-29 8:49 ` tiejun.chen
2010-09-29 21:24 ` david.hagood
2010-10-08 9:22 ` tiejun.chen
2010-10-08 11:16 ` David Hagood [this message]
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=1286536572.2545.16.camel@chumley \
--to=david.hagood@gmail.com \
--cc=iws@ovro.caltech.edu \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.com \
--cc=tiejun.chen@windriver.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 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).