Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756696AbXKNKAd (ORCPT ); Wed, 14 Nov 2007 05:00:33 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753252AbXKNKAO (ORCPT ); Wed, 14 Nov 2007 05:00:14 -0500 Received: from fgwmail5.fujitsu.co.jp ([192.51.44.35]:58097 "EHLO fgwmail5.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753081AbXKNKAM (ORCPT ); Wed, 14 Nov 2007 05:00:12 -0500 Message-ID: <473AC609.2050204@jp.fujitsu.com> Date: Wed, 14 Nov 2007 18:55:21 +0900 From: Kenji Kaneshige User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Matthew Wilcox Cc: Kristen Carlson Accardi , Greg KH , Rick Jones , Greg KH , Alex Chiang , lenb@kernel.org, linux-kernel@vger.kernel.org, linux-pci@atrey.karlin.mff.cuni.cz, pcihpd-discuss@lists.sourceforge.net, linux-acpi@vger.kernel.org Subject: Re: [PATCH 0/5][RFC] Physical PCI slot objects References: <20071113000853.GA13341@ldl.fc.hp.com> <20071113170129.GA20185@kroah.com> <20071113202154.GA22812@ldl.fc.hp.com> <20071113202632.GA3227@kroah.com> <473A2A61.7030303@hp.com> <20071113225605.GA2589@suse.de> <20071113230400.GP17785@parisc-linux.org> <20071113153314.ba46cdf0.kristen.c.accardi@intel.com> <20071114001008.GQ17785@parisc-linux.org> In-Reply-To: <20071114001008.GQ17785@parisc-linux.org> Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7BIT Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1289 Lines: 31 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/