Date: Wed, 29 Mar 1995 13:58:25 -0500 (EST) From: Peter Dufault <dufault@hda.com> To: terry@cs.weber.edu (Terry Lambert) Cc: darrenr@vitruvius.arbld.unimelb.edu.au, freebsd-hackers@freefall.cdrom.com Subject: Re: Configuring driver added via LKM Message-ID: <199503291858.NAA00450@hda.com> In-Reply-To: <9503291825.AA20071@cs.weber.edu> from "Terry Lambert" at Mar 29, 95 11:25:07 am
next in thread | previous in thread | raw e-mail | index | archive | help
Terry Lambert writes: > > > No, I disagree. That logic shouldn't be LKM code that isn't present > > in a config'd driver, it should be a standard driver entry point > > similar to probe and attach. > > In the case of Win95, this entry point is called by what they call > a "volume tracking driver"; basically, something that knows about > stuff "going away". (...) Whew. I'll save that for when I have a beer. I added "isa_device_install" and "isa_device_remove" to isa.c, and a "detach" complement to "attach" in the isa_driver structure. The rule is you have to call detach in a context that you can sleep so that you can allow your device to go idle. This is obviously not sufficient for when someone pops out the scsi adapter with a mounted disk. I'm happily adding and removing the .o for my drivers with this change and this is all I wanted. I understand your concern about minimal convenience changes getting you nowhere - you may never reach a global maxima if you keep taking only locally maximizing steps. Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199503291858.NAA00450>