From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+w=401wt.eu-S1762771AbXKNSi7@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1762771AbXKNSi7 (ORCPT <rfc822;w@1wt.eu>);
	Wed, 14 Nov 2007 13:38:59 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1761118AbXKNSiu
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Wed, 14 Nov 2007 13:38:50 -0500
Received: from mga02.intel.com ([134.134.136.20]:34766 "EHLO mga02.intel.com"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1763106AbXKNSis (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Wed, 14 Nov 2007 13:38:48 -0500
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="4.21,417,1188802800"; 
   d="scan'208";a="271005593"
Date: Wed, 14 Nov 2007 10:38:09 -0800
From: Kristen Carlson Accardi <kristen.c.accardi@intel.com>
To: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Cc: Matthew Wilcox <matthew@wil.cx>, Greg KH <gregkh@suse.de>,
       Rick Jones <rick.jones2@hp.com>, Greg KH <greg@kroah.com>,
       Alex Chiang <achiang@hp.com>, 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
Message-Id: <20071114103809.ed0c36ef.kristen.c.accardi@intel.com>
In-Reply-To: <473AC609.2050204@jp.fujitsu.com>
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>
	<473AC609.2050204@jp.fujitsu.com>
X-Mailer: Sylpheed 2.3.1 (GTK+ 2.10.13; i386-redhat-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

On Wed, 14 Nov 2007 18:55:21 +0900
Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com> 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.