On Sat, May 02, 2009 at 08:11:38AM +0000, Lifesaver wrote:
> I have a board which sits on PCIe slot of a x86 machine running 2.6 kernel. My
> goal is to get a consistent way of identifying the physical slot ID from the
> pci_dev structure associated with a device on the board (multiple devices).
> When I do an lspci -t , the device shows up this:
>
> 0x1c ----- 0xa ------- 0x9
> |
> |--device 1
> |--device 2 and so on
>
>
> When I walk thru the bus with a while loop
>
> bus = pDev->bus;
> do
> {
> printk (.... "bus number : %x", bus->number )
Try adding:
printk("slot number : %x", PCI_SLOT(bus->self->devfn));
>
> } while (bus = bus->parent)
>
> I get 0x9 , 0xa , 0x0
>
> I have tried almost all of the feilds of bus , even tried traversing thru
> bus_list, but I cant get that 0x1c programmetically. 0x1c is probably the bus
> number for PCI-PCIe bridge, most fields of bus structure become 0 for this.. Is
> there a easy way to get this via pci_dev structure?
>
> Thanks
>
> --
> 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
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
--
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
