* Greg KH <greg@xxxxxxxxx>: > On Mon, Jan 25, 2010 at 09:27:18PM -0700, Alex Chiang wrote: > > * Greg KH <greg@xxxxxxxxx>: > > > On Mon, Jan 25, 2010 at 09:57:45AM -0800, Gary Hade wrote: > > > > > > > > Andreas, Would the physical slot number to PCI ID mapping > > > > provided in /sys/bus/pci/slots by the 'pci_slot' driver possibly > > > > be of any use to you? > > > > > > That mapping should be already there if it is provided by the BIOS. > > > > Where? Somewhere else in sysfs? > > > > /sys/bus/pci/slots/ only gets populated when a hotplug driver or > > pci_slot are loaded. > > > > And if those slots aren't hotplug capable, then that directory > > won't get populated. > > Ah, I was thinking of the pci_slot stuff. Gah, I was attempting to clarify, but instead made things worse. If the slots aren't physically capable of hotplug, then loading a hotplug driver (pciehp, acpiphp, shpchp, etc.) will not populate the directory. However, you may still have a chance at populating the directory if the slots are described in ACPI by the BIOS. > > Finally, if the slots aren't described by ACPI, that directory > > also won't get populated. In that scenario -- non hotplug slots, but described by ACPI -- you can modprobe pci_slot and you will indeed get entries in /sys/bus/pci/slots/ sorry for the confusion. :( /ac -- 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
