Daemon News Ezine BSD News BSD Mall BSD Support Forum BSD Advocacy BSD Updates

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

DRIVER_UNIDENTIFY



How about creating a new driver_if.m entry point that is the complement to 
DRIVER_IDENTIFY.  I would call it DRIVER_UNIDENTIFY() and would change 
bus_generic_detach() to call it on each driver similar to how 
bus_generic_probe() currently calls DRIVER_IDENTIFY() for each driver.  This 
would allow drivers that create devices in DRIVER_IDENTIFY() have a place to 
remove the device when they are unloaded.

-- 
John Baldwin <jhb@xxxxxxxxxxx>  <><  http://www.FreeBSD.org/~jhb/
"Power Users Use the Power to Serve"  =  http://www.FreeBSD.org