From owner-freebsd-hackers Wed Oct 4 03:52:06 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id DAA09196 for hackers-outgoing; Wed, 4 Oct 1995 03:52:06 -0700 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id DAA09191 for ; Wed, 4 Oct 1995 03:52:04 -0700 Received: (from julian@localhost) by ref.tfs.com (8.6.11/8.6.9) id DAA02038 for hackers@freebsd.org; Wed, 4 Oct 1995 03:52:03 -0700 From: Julian Elischer Message-Id: <199510041052.DAA02038@ref.tfs.com> Subject: some forward progress on dynamic devices To: hackers@freebsd.org Date: Wed, 4 Oct 1995 03:52:02 -0700 (PDT) X-Mailer: ELM [version 2.4 PL24] Content-Type: text Content-Length: 817 Sender: owner-hackers@freebsd.org Precedence: bulk I've been working on integrating some TFS proprietary hardware with FreeBSD. Using devfs and the cdevsw_add() routines I am able to link the devices in with no changes to the sources off the net, other than to add the files to i386/conf/file.i386.. no-more having to edit conf.c no more editing /dev/MAKEDEV .. yey! A little cleaning up to do then I'm planning on launching into ALL THE DEVICES and adding similar dynamic stuff (ifdef'ed out by default) the aim is to be able to flick a switch and go fully dynamic, but until then I want to make sure nothing breaks. in this app they can't be lkms.. but it'd be nice.. I think the next hurdle to be cleared is fully dynamic interrupt assignment, so an lkm driver can dynamically decide which vector and which ipl.. this is starting to be fun again.. julian