ppbus probe problem
M. Warner Losh
imp at bsdimp.com
Thu Mar 18 06:10:54 PST 2004
In message: <200403181012.43455.dfr at nlsystems.com>
Doug Rabson <dfr at nlsystems.com> writes:
: On Thursday 18 March 2004 10:05, Guido van Rooij wrote:
: > On Thu, Mar 18, 2004 at 09:13:33AM +0000, Doug Rabson wrote:
: > > I would use something like:
: > >
: > > static void
: > > vpo_identify(driver_t *driver, device_t parent)
: > > {
: > > device_t dev;
: > >
: > > dev = device_find_child(parent, "vpo", 0);
: > > if (!dev)
: > > BUS_ADD_CHILD(parent, 0, "vpo", -1);
: > > }
: >
: > So I'll update all of the ppbus drivers that way. Okay?
:
: I think so. Warner, do you have any objections?
No.
: In an ideal world, there should be some kind of BUS_UNIDENTIFY method
: which a driver could use to delete the devices it created in
: BUS_IDENTIFY.
Or the bus would have a driver deleted routine that got called and it
would remove all instances of the devclass attached to it.
Warner
More information about the freebsd-new-bus
mailing list