> The drivers simply check the ID and say whether they can drive it or
> not. So the identification needs to be in the driver's match routine,
> not in the parent podulebus routines.

One slight correction:

The say whether they can drive it, and can indicate how close a match
the driver is to the hardware by their return value.

This can be used so that 'best' drivers are automatically picked: a
generic driver that matches a whole class of devices can return a low
but non-zero 'match' value, while a better, more specific driver can
return a higher match value.  The driver with the higest (non-zero)
match value will be used to drive the device.


This description also has the caveat that other busses may be
configured differently, but you did say you were talking about the
podule bus.  8-)



chris