Guido van Rooij a5c7e3bb70 Prevent the strange situation that after each load/unload of a ppbus ... device, the device is probed multiple times (so each device is detected N times after unloading/loading the module N-1 times). The real fix is (quote Doug and Warner): > : 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. Reviewed by: Doug Rabson & Warner Losh		2004-03-18 21:10:11 +00:00
..
if_plip.c	Prevent the strange situation that after each load/unload of a ppbus	2004-03-18 21:10:11 +00:00
immio.c
lpbb.c	Prevent the strange situation that after each load/unload of a ppbus	2004-03-18 21:10:11 +00:00
lpt.c	Prevent the strange situation that after each load/unload of a ppbus	2004-03-18 21:10:11 +00:00
lpt.h
lptio.h
pcfclock.c	Prevent the strange situation that after each load/unload of a ppbus	2004-03-18 21:10:11 +00:00
ppb_1284.c
ppb_1284.h
ppb_base.c
ppb_msq.c
ppb_msq.h
ppbconf.c
ppbconf.h
ppbio.h
ppbus_if.m
ppi.c	Prevent the strange situation that after each load/unload of a ppbus	2004-03-18 21:10:11 +00:00
ppi.h
pps.c	Prevent the strange situation that after each load/unload of a ppbus	2004-03-18 21:10:11 +00:00
vpo.c	Prevent the strange situation that after each load/unload of a ppbus	2004-03-18 21:10:11 +00:00
vpoio.c
vpoio.h