[PATCH] powerpc/fsl-pci: fix pcie range issue for some P1/P2 boards
B48286 at freescale.com
Wed Jul 29 12:34:32 AEST 2015
Hi Scott and all,
Please ignore this patch!
> -----Original Message-----
> From: Wood Scott-B07421
> Sent: 2015年7月25日 10:48
> To: Hou Zhiqiang-B48286
> Cc: linuxppc-dev at lists.ozlabs.org; benh at kernel.crashing.org;
> paulus at samba.org; mpe at ellerman.id.au; Hu Mingkai-B21284
> Subject: Re: [PATCH] powerpc/fsl-pci: fix pcie range issue for some P1/P2
> On Wed, 2015-07-22 at 18:08 +0800, Zhiqiang Hou wrote:
> > From: Hou Zhiqiang <B48286 at freescale.com>
> You CCed this to
> b21284 at 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
> 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?
Yes, you're right. It isn't an issue using 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
More information about the Linuxppc-dev