@Scott Wood, as requested, a new thread for my PCI issues
I've got a heavily-patched version of 3.18.13 that works great on a custom P5020-based ATX board. When I boot 3.19-rc2, I get the following
PCI: Cannot allocate resource region 0 of device 0000:00:00.0, will remap
PCI: Cannot allocate resource region 0 of device 0001:00:00.0, will remap
PCI: Cannot allocate resource region 6 of device 0001:08:00.0, will remap
pci 0000:00:00.0: BAR 0: no space for [mem size 0x01000000]
pci 0000:00:00.0: BAR 0: failed to assign [mem size 0x01000000]
pci 0000:01:00.0: BAR 6: assigned [mem 0xc10040000-0xc1005ffff pref]
Are there any patchsets you can point me at which may not be upstream yet, that would resolve this issue?
Full kernel boot output with 3.19-rc2 at http://pastie.org/private/njlwhfkzulkmy6cau1i8ig
my kernel .config is at http://www.alexperez.com/Cyrus-P5020-3.19-rc2-config.txt
Sorry for the delay. Could you elaborate on what fails to work with PCIe? I see similar messages but PCIe devices still work. The "will remap" lines are not errors -- they are expected in the case where firmware didn't set up usable mappings. As for BAR 0 of 00:00.0, that's always bit a bit weird on Freescale PCI controllers. Other devices seem to have their BARs assigned OK from the log.
What is the output of "lspci -v" after booting?
scottwood, lspci -v shows zero output. There is not even a root device. Kernels up to and including 3.19-rc7 (released yesterday) do not seem to include functional PCI or SATA. I think there's some backsliding going on with regards to upstream support for SATA as well, as it works in 3.18.5, but not in 3.19-rcX
scottwood This is still a problem with the final release of 3.19. As an aside, the on-board SATA does not work with 3.19 either, but worked fine in 3.18, so we have a regression on that front. With kernel 3.18.1, lspci -v also shows no output. PCI worked in 3.17.