From owner-freebsd-current Wed May 7 06:54:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA23333 for current-outgoing; Wed, 7 May 1997 06:54:33 -0700 (PDT) Received: from nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA23328 for ; Wed, 7 May 1997 06:54:29 -0700 (PDT) Received: from herring.nlsystems.com (herring.nlsystems.com [10.0.0.2]) by nlsystems.com (8.8.5/8.8.5) with SMTP id OAA09355 for ; Wed, 7 May 1997 14:55:13 +0100 (BST) Date: Wed, 7 May 1997 14:55:13 +0100 (BST) From: Doug Rabson Reply-To: Doug Rabson To: current@freebsd.org Subject: Backwards compatibiliy for isa_driver Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk So far in my modularisation work, I have managed to keep a high level of binary compatibility (and a moderate level of source compatibility) with previous releases. The structures isa_device and isa_driver and all low-level functions in isa.c are unchanged. In particular my binary release of OSS still works :-). Unfortunately the situation with isa_driver is getting pretty ugly and I *really* want to add a detach function to it. If I add a detach function to it, I'm going to add a bunch of other stuff to simplify some of the rest of the code. My question is, how much will break if I change isa_driver? I think OSS will still work from looking at its symbol table since it calls register_intr directly instead of going through config_isadev. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 951 1891