[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20071113153314.ba46cdf0.kristen.c.accardi@intel.com>
Date: Tue, 13 Nov 2007 15:33:14 -0800
From: Kristen Carlson Accardi <kristen.c.accardi@...el.com>
To: Matthew Wilcox <matthew@....cx>
Cc: 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
On Tue, 13 Nov 2007 16:04:00 -0700
Matthew Wilcox <matthew@....cx> wrote:
> On Tue, Nov 13, 2007 at 02:56:05PM -0800, Greg KH wrote:
> > Why not just use the code in the linux firmware kit that does this
> > already today from userspace (thanks to Kristen for pointing this out to
> > me on irc.)?
>
> So then we have something that works on ACPI-based machines. Who will
> add support for all the other kinds of firmware and non-firmware based
> slots?
>
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.
-
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