On Tue, Dec 06, 2016 at 02:46:00PM -0500, Jon Masters wrote:
On 12/05/2016 04:21 PM, Bjorn Helgaas wrote:
quoted
On Fri, Dec 02, 2016 at 07:33:46PM -0500, Jon Masters wrote:
quoted
quoted
quoted
Even without this patch, I don't think it's a show-stopper to have
Linux mistakenly thinking this region is routed to PCI, because the
driver does reserve it and the PCI core will never try to use it.
Ok. So are you happy with pulling in Duc's v4 patch and retaining
status quo on the bridge resources for 4.10?
Yes, I think it looks good. I'll finish packaging things up and
repost the current series.
Ok, great. So you're still pretty confident we'll have "out of the box"
booting on these machines for 4.10? :)
I just merged pci/ecam into my "next" branch, so as long as tomorrow's
linux-next boots out of the box, we should be set. I made the following
changes compared to v11:
- dropped the x86 change to use acpi_resource_consumer()
- added parens around macro args used in arithmetic expressions
- renamed "seg" to "node" in THUNDER_PEM_RES and THUNDER_PEM_QUIRK
- incorporated (u64) cast and dropped "UL" postfix for THUNDER_PEM_QUIRK
Let me know if you see any issues.
Bjorn