Re: [PATCH v10 02/59] sparc/PCI: Use correct bus address to resource offset

2016-03-18 Thread Yinghai Lu
On Sat, Mar 12, 2016 at 3:26 AM, Bjorn Helgaas wrote: > On Sat, Mar 12, 2016 at 12:22:06AM -0800, Yinghai Lu wrote: >> Good findings, that would break the sparc for a while. >> (we should use res->start instead) > > We haven't even gotten to the part that your patch changes. If my > analysis is

Re: [PATCH v10 02/59] sparc/PCI: Use correct bus address to resource offset

2016-03-12 Thread Bjorn Helgaas
On Sat, Mar 12, 2016 at 12:22:06AM -0800, Yinghai Lu wrote: > On Thu, Mar 10, 2016 at 10:24 AM, Bjorn Helgaas wrote: > >> pci_sun4v f02ae7f8: PCI host bridge to bus :00 > >> pci_bus :00: root bus resource [io 0x2007e-0x2007e0fff] > >> (bus address [0x-0xfff]) > > > >

Re: [PATCH v10 02/59] sparc/PCI: Use correct bus address to resource offset

2016-03-12 Thread Yinghai Lu
On Thu, Mar 10, 2016 at 10:24 AM, Bjorn Helgaas wrote: >> pci_sun4v f02ae7f8: PCI host bridge to bus :00 >> pci_bus :00: root bus resource [io 0x2007e-0x2007e0fff] >> (bus address [0x-0xfff]) > > Just double-checking that your ioport space really contains 256M ports.

Re: [PATCH v10 02/59] sparc/PCI: Use correct bus address to resource offset

2016-03-10 Thread David Miller
From: Bjorn Helgaas Date: Thu, 10 Mar 2016 12:24:40 -0600 > Hi Yinghai, > > On Wed, Feb 24, 2016 at 06:11:53PM -0800, Yinghai Lu wrote: >> After we add 64bit mmio parsing, we got some "no compatible bridge window" >> warning on anther new model that support 64bit resource. >> >> It turns out th

Re: [PATCH v10 02/59] sparc/PCI: Use correct bus address to resource offset

2016-03-10 Thread Bjorn Helgaas
Hi Yinghai, On Wed, Feb 24, 2016 at 06:11:53PM -0800, Yinghai Lu wrote: > After we add 64bit mmio parsing, we got some "no compatible bridge window" > warning on anther new model that support 64bit resource. > > It turns out that we can not use mem_space.start as 64bit mem space > offset, aka the