From: Scott Wood <scottwood@freescale.com>
To: Zhiqiang Hou <B48286@freescale.com>
Cc: <linuxppc-dev@lists.ozlabs.org>, <benh@kernel.crashing.org>,
<paulus@samba.org>, <mpe@ellerman.id.au>, <b21284@freescale.com>
Subject: Re: [PATCH] powerpc/fsl-pci: fix pcie range issue for some P1/P2 boards
Date: Fri, 24 Jul 2015 21:48:24 -0500 [thread overview]
Message-ID: <1437792504.2993.280.camel@freescale.com> (raw)
In-Reply-To: <1437559704-13332-1-git-send-email-B48286@freescale.com>
On Wed, 2015-07-22 at 18:08 +0800, Zhiqiang Hou wrote:
> From: Hou Zhiqiang <B48286@freescale.com>
You CCed this to
b21284@freescale.com. Who is that? It would be nice to use "friendly"
e-mail addresses, but at least include the name along with the e-mail address.
I suggest CCing the people who added these device trees.
> Impact board list:
> P1020MBG-PC. P1022DS, P2020RDB
> All above boards have its PCIE memory range less than 0xbfff_ffff,
If you mean that the physical address of the memory region is <= 0xbfff_ffff,
I don't see the relevance.
> but in dts its boundary value was 0xe0000000. Both of them was maped
> to the same boundary 0xe0000000 which was Overlapped and crossed.
By "boundary" do you mean the PCIe bus address? Why is it a problem for
these independent PCIe root complexes to have the same PCIe bus addresses?
> Cpu will access the illicit memery addr and detect error then lead to
> cpu stall. So update dts for these boards.
What is illicit about it?
Why isn't the problem seen in the 36-bit device trees, which do the same
thing?
-Scott
next prev parent reply other threads:[~2015-07-25 2:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-22 10:08 [PATCH] powerpc/fsl-pci: fix pcie range issue for some P1/P2 boards Zhiqiang Hou
2015-07-25 2:48 ` Scott Wood [this message]
2015-07-29 2:34 ` Hou Zhiqiang
2015-07-29 2:35 ` Scott Wood
2015-07-30 10:02 ` Hou Zhiqiang
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=1437792504.2993.280.camel@freescale.com \
--to=scottwood@freescale.com \
--cc=B48286@freescale.com \
--cc=b21284@freescale.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.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).