On Wed, Dec 04, 2002 at 12:04:41PM -0600, James Bottomley wrote:
> greg@kroah.com said:
> > But doesn't the bus specific core know when drivers are attached, as
> > it was told to register or unregister a specific driver? So I don't
> > see why this is really needed.
>
> The problem is that the bus specific core registration no-longer knows if the
> probes succeeded or failed (and if they did, what devices were attached),
> since probing is controlled by the base core.
Not quite. Well, I guess you can modify all of your drivers to do this,
but see below for an easier way.
> What the bus needs to know is when a driver attaches to a specific device (and
> what device it has attached to).
Why not have a call in the driver that notifies the bus specific core of
this? Or just check the status of the return value of your "probe"
function that the bus provides. See usb_device_probe() and
pci_device_probe() for examples of this.
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Sat Dec 07 2002 - 22:00:19 EST