On Fri, 2008-05-30 at 13:00 -0600, Alex Chiang wrote: > > We're using the combination of pci_bus and devfn to keep track of > slots we've created. If each pseries slot is its own pci_bus, > then faking in a 0 devfn for unpopulated slots at the least won't > be harmful. > > Once a device is plugged into the slot, then the slot's pci_bus > would have two entries, the fake 0 devfn and the real devfn of > the actual device. Sounds a bit gross tho .. Can we "update" the slot's devfn ? What is the devfn used for internally in the new architecture ? I'll dig into the code (it's monday morning, haven't looked yet, just unpiling the week-end's emails :-) Ideally, if we want to uniquely identify slots, we should use something else on pSeries. We do get some slot number information for example from the firmware (it's a big ugly string tho, not just an integer). Cheers, Ben. -- 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
