On Fri, Aug 30, 2013 at 12:46:27PM -0700, Yinghai Lu wrote: > On Fri, Aug 30, 2013 at 1:01 AM, Johannes Thumshirn > <johannes.thumshirn@xxxxxx> wrote: > > > > I'll test on mainline and then check pci-busn-alloc, but I have this strange > > feeling that it could be an interaction with Freescale's DPAA Ethernet, which is > > not yet merged into mainline. > > please try for-pci-busn-alloc at > git://git.kernel.org/pub/scm/linux/kernel/git/yinghai/linux-yinghai.git > for-pci-busn-alloc-3.11 > > it is based on linus's tree + pci/next > > Yinghai Hi Yinghai, I've tested the board with your for-pci-busn-alloc-3.11 branch. Initial enumeration is just as it was before. With the difference that a "sysfs-rescan" now results in: root@generic-powerpc:~# lspci 00:00.0 PCI bridge: Freescale Semiconductor Inc P4080 (rev 20) root@generic-powerpc:~# echo 1 > /sys/bus/pci/rescan pci_bus 0000:00: scanning bus pcieport 0000:00:00.0: scanning [bus 01-01] behind bridge, pass 0 pcieport 0000:00:00.0: scanning [bus 00-00] behind bridge, pass 1 pcieport 0000:00:00.0: rescan scaned bridge as broken one again ? pci_bus 0000:00: bus scan returning with max=00 root@generic-powerpc:~# lspci 00:00.0 PCI bridge: Freescale Semiconductor Inc P4080 (rev 20) The good news for me is, I can work on your tree to try to resolve the issue. Johannes -- To unsubscribe from this list: send the line "unsubscribe linux-pci" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
