From owner-freebsd-hackers Wed Mar 29 02:45:09 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id CAA10011 for hackers-outgoing; Wed, 29 Mar 1995 02:45:09 -0800 Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.34]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id CAA09935 for ; Wed, 29 Mar 1995 02:45:00 -0800 Received: (from bde@localhost) by godzilla.zeta.org.au (8.6.9/8.6.9) id UAA27247; Wed, 29 Mar 1995 20:43:15 +1000 Date: Wed, 29 Mar 1995 20:43:15 +1000 From: Bruce Evans Message-Id: <199503291043.UAA27247@godzilla.zeta.org.au> To: dufault@hda.com Subject: Re: Configuring driver added via LKM Cc: freebsd-hackers@freefall.cdrom.com Sender: hackers-owner@FreeBSD.org Precedence: bulk >Is it on purpose that "id_alive" isn't set if you are reconfiguring >a device in "isa/isa.c"? Is there an entry point for "I'm about >to remove you"? `id_alive' was originally just to record devices that have been successfully probed and attached so that the conflict checking knows which devices to look at. This got complicated a bit by the reconfig stuff. I'm not familiar enough with that to comment on it. >How completely thrashed out is registering a device with the kernel >(completely, including using Garrett's devconf routines) and then >de-registering it in order to completely clean up and register >again? Almost no work has been done one it (before you started :-). isa_config() and config_isadev_c() are very old and barely enough to configure isa devices. I expect they will have to be rewritten to handle dynamic attachment and detachment. In particular, the second half of isa_config() assumes that the probes and attaches are complete. Bruce