[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20071114001008.GQ17785@parisc-linux.org>
Date: Tue, 13 Nov 2007 17:10:08 -0700
From: Matthew Wilcox <matthew@....cx>
To: Kristen Carlson Accardi <kristen.c.accardi@...el.com>
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, 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.
I don't understand how you're supposed to get the slot number for
standard PCI for occupied slots. Could you explain?
--
Intel are signing my paycheques ... these opinions are still mine
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
-
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