On Thu, Feb 7, 2013 at 11:15 AM, Jason Gunthorpe <jgunthorpe@xxxxxxxxxxxxxxxxxxxx> wrote: > On Thu, Feb 07, 2013 at 11:08:45AM -0700, Bjorn Helgaas wrote: > >> I think the way you'll have to fix this in the meantime is to use >> pci_create_root_bus() directly so you can do things in this sequence: >> >> pci_create_root_bus >> pci_scan_child_bus >> pci_bus_assign_resources >> pci_bus_add_devices >> >> dino_probe() is an example of similar code that does this. > > Erm, but isn't this problem going to strike any system that doesn't > have resources assigned by the firmware? > > If so, a common 'pci_scan_bus_from_scratch' would at least highlight > the problem and centralize the work around until it is fixed... > > Many embedded systems will require this.. Yep, agreed on all counts. -- 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
