Joerg Wunsch 6044485346 More cleanup when detaching. Clone device entries will now be ... destroyed properly (otherwise bad things would happen after a clone dev had been created, and the module was kldunloaded). Allocated children that have not successfully probed are being deleted again (otherwise fd0 and fd1 have always been allocated, even if only fd0 was acutally present, and fd1 even survived kldunloading the module). Still, kldunloading leaves remnants of the previously existing devices intact. Why doesn't it destroy all the devices? As a consequence, since dev->descr now points into no longer allocated memory, the system panics deep inside printf(9) when running devinfo(1) after kldunloading the module. Ideas sought... Also, when kldloading the module on a hints-populated isab0, this bus somehow has already created an fdc0 entry (a dummy) so the load attempt fails and will register fdc1 instead. What are those dummy entries for? Loading the module from the bootloader works, and it can be unloaded an re-loaded then later.		2001-07-04 22:10:33 +00:00
..
fdc.c	More cleanup when detaching. Clone device entries will now be	2001-07-04 22:10:33 +00:00
fdcreg.h	Move out the files from src/sys/isa/ic/ to src/sys/dev/ic/, so they	2001-06-04 21:04:14 +00:00