You have to ask the right person. :-) I've been defacto mainainingthe rpaphp code for unpteen years now. On the other hand, I am alsomuch, much better at promising than delivering.

> This is one of the hateful things about the current design -- hotplug> drivers do too much. Instead of being just the interface between the> Linux PCI code and the hardware, they create sysfs directories, add> files,> and generally have far too much freedom.

I chopped out several hundred LOC from rpaphp a year ago,and hopefuly that might make furthre simplification easier someday.

> We have four different schemes currently for naming in slots/,> 1. slot number. Used by cpqphp, ibmphp, acpiphp, pciehp, shpc.> 2. domain:bus:dev:fn. Used by fakephp.> 3a. domain:bus:dev. Used by rpaphp and sgihp.> 3b. Except that rpaphp uses phy_location to present the information> that> should be in the name and sgihp uses path.>> ... I've forgotten what cpci uses. And yenta doesn't use it.>> How is anyone supposed to write sane managability tools in the> presence> of such anarchy?>> > ~ # cat /sys/bus/pci/slots/0000:00:02.2/phy_location> > U787A.001.DNZ00Z5-P1-C2>> Right. This should look like:>> # cat /sys/bus/pci/slots/U787A.001.DNZ00Z5-P1-C2/address> 0000:00:02

This patch implements exactly what you describe. Boot tested.I assume you really mean it -- if so, then please review andack the patch !?

I have absolutely no clue if this breaks any existing IBM tools.I'm pretty sure it doesn't ... but attention Mike Strosaker! does it?