On Wed, 14 Nov 2007 18:55:21 +0900 Kenji Kaneshige <kaneshige.kenji@xxxxxxxxxxxxxx> wrote: > Matthew Wilcox ????????: > > On Tue, Nov 13, 2007 at 03:33:14PM -0800, Kristen Carlson Accardi wrote: > >> As far as being able to retrieve the slot number (which it seemed from > >> the HP manageablity application perspective is the goal here), that > >> information is available from userspace as well for at least standard PCI > >> and pcie based systems for occupied slots. For standard pci, you have > >> to make something up anyway - for shpchp we just use an incremental > >> number and combine it with the bus number to represent the slot. For > >> pcie, you can get this info from the slot capabilities register. > > > > Ummm ... that's not what the /spec/ says. I've never worked on any shpc > > machines, but the shpc driver reads the slot values from the SLOT_CONFIG > > register, just like the spec says to. > > > > The slot number for shpc slot is like 'YYYY_XXXX'. > > YYYY is the bus number, though I don't know the specific reason > why it was added. > > XXXX is slot number decided according to the shpc specification, > as you said. > > Thanks, > Kenji Kaneshige > Kenji is correct, you should listen to him, not me :). For standard PCI slots that are not hotplug, I would think you'd need firware support to find the slot numbers -- but I'm not sure on this. btw - the YYYY was added to prevent duplicate slot numbers on buggy machines btw. - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
