PCI Hotplug Slot Naming Scheme

[Greg KH]

On Fri, Mar 26, 2004 at 12:50:13PM -0600, linas at austin.ibm.com wrote:
> On Fri, Mar 26, 2004 at 08:42:26AM -0800, Greg KH wrote:
> > On Fri, Mar 26, 2004 at 10:31:38AM -0600, John Rose wrote:
> > >
> > >    # ls /sys/bus/pci/slots
> > >    ..   U7311.D11.104CE9A-P1-C1  U7879.001.DQD0027-P1-C2
> > >    U7311.D11.104CE9A-P1-C2  U7879.001.DQD0027-P1-C3
> > >    U7311.D11.104CE9A-P1-C3  U7879.001.DQD0027-P1-C4
> > >    U7311.D11.104CE9A-P1-C5  U7879.001.DQD0027-P1-C5
> > >    U7311.D11.104CE9A-P1-C6  U7879.001.DQD0027-P1-C6
> > >    U7311.D11.104CE9A-P1-C7  U9117.570.104F3DC-V1-C0
> > >
> > >    These are just 23 chars long, imagine 48.
> >
> > Ick, ick, ick.  I say no.  Those names mean nothing to anyone familiar
> > with Linux.
>
> Yes, but they do mean something to the sysadmin who has to figure out
> the physical location of some device.

Then don't reinvent the wheel and do what the acpi pci hotplug driver
does today and put that system specific information into a file in the
slot directory.

> In particular, the HMC does not use the Linux naming scheme.   There's
> need for both until more sophisticated management tools can be
> developed.

Hm, pcihpview handles the acpi stuff just fine today.  It would also
handle the ppc64 driver just as well.

thanks,

greg k-h

** Sent via the linuxppc64-dev mail list. See http://lists.linuxppc.org/