matthew green <mrg@eterna.com.au> writes:
   > would you expand more on how you would expect this to work?  i can't
   > think of anything i don't immediately shudder at.
   
   maybe it makes you shudder, but something as simple as code that fills
   in, or returns an array of 32 (signed) chars that indicate ordering
   could do the trick.  array entry value is slot number.  -1 means 'skip
   this array entry'.
   
   It's not pretty... but neither is stuffing random firmware crud into
   the PCI layer.  8-)
   
   Also consider that probe ordering is a more general problem than "just
   an OFW thing."  it makes sense for lots of HW where you know the
   on-board device numbers...  and the best way to get that info is an MD
   hook.


OK, that could work.


the one remaining problem is getting the OFW node for children that need
it, such as the ebus on sparc64.  i'd really like to get rid of the hack
that finds the `ebus' node from that driver...