From owner-freebsd-hackers Tue Mar 28 16:24:02 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id QAA01346 for hackers-outgoing; Tue, 28 Mar 1995 16:24:02 -0800 Received: from hda.com (hda.com [199.232.40.182]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id QAA01338 for ; Tue, 28 Mar 1995 16:23:59 -0800 Received: (dufault@localhost) by hda.com (8.6.9/8.3) id TAA00578; Tue, 28 Mar 1995 19:24:19 -0500 From: Peter Dufault Message-Id: <199503290024.TAA00578@hda.com> Subject: Re: Configuring driver added via LKM To: dufault@hda.com (Peter Dufault) Date: Tue, 28 Mar 1995 19:24:18 -0500 (EST) Cc: freebsd-hackers@freefall.cdrom.com In-Reply-To: <199503282026.PAA01042@hda.com> from "Peter Dufault" at Mar 28, 95 03:26:31 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 828 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"? 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? I may be missing something, but I don't see a set of entry points that look like there are many people adding and removing device drivers for debug. I'd like the device driver code to remain completely clean without any conditionals for the LKM. If anyone has any pointers I'd appreciate them. Peter -- Peter Dufault Real Time Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 dufault@hda.com Fax: 508 433 5267