[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <473AC609.2050204@jp.fujitsu.com>
Date: Wed, 14 Nov 2007 18:55:21 +0900
From: Kenji Kaneshige <kaneshige.kenji@...fujitsu.com>
To: Matthew Wilcox <matthew@....cx>
Cc: Kristen Carlson Accardi <kristen.c.accardi@...el.com>,
Greg KH <gregkh@...e.de>, Rick Jones <rick.jones2@...com>,
Greg KH <greg@...ah.com>, Alex Chiang <achiang@...com>,
lenb@...nel.org, linux-kernel@...r.kernel.org,
linux-pci@...ey.karlin.mff.cuni.cz,
pcihpd-discuss@...ts.sourceforge.net, linux-acpi@...r.kernel.org
Subject: Re: [PATCH 0/5][RFC] Physical PCI slot objects
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists