From owner-freebsd-isdn@FreeBSD.ORG Sat Feb 26 19:13:55 2005 Return-Path: Delivered-To: freebsd-isdn@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id BEC0116A4CE for ; Sat, 26 Feb 2005 19:13:55 +0000 (GMT) Received: from swip.net (mailfe06.swip.net [212.247.154.161]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B78F43D3F for ; Sat, 26 Feb 2005 19:13:54 +0000 (GMT) (envelope-from hselasky@c2i.net) X-T2-Posting-ID: gvlK0tOCzrqh9CPROFOFPw== Received: from mp-217-230-217.daxnet.no ([193.217.230.217] verified) by mailfe06.swip.net (CommuniGate Pro SMTP 4.2.9) with ESMTP id 303654155; Sat, 26 Feb 2005 20:13:52 +0100 From: Hans Petter Selasky To: freebsd-isdn@freebsd.org Date: Sat, 26 Feb 2005 20:14:33 +0100 User-Agent: KMail/1.7 References: <20050226004635.GA2922@odin.ac.hmc.edu> In-Reply-To: <20050226004635.GA2922@odin.ac.hmc.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200502262014.36481.hselasky@c2i.net> cc: Brooks Davis Subject: Re: mechanical i4b cleanups X-BeenThere: freebsd-isdn@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: hselasky@c2i.net List-Id: Using ISDN with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 26 Feb 2005 19:13:55 -0000 On Saturday 26 February 2005 01:46, Brooks Davis wrote: > Below are some fairly mechanical patches I did 6-9 months ago to drag > some of i4b's drivers in the direction of a modern implementation. I > don't have the ability to test them and I don't have time to work on > them. Perhaps someone here does. > > The patches are also at: > > http://people.freebsd.org/~brooks/patches/i4b.diff > > -- Brooks > If you want to modulize the devices in i4b/drivers you need some kind of i4b_driver_attach() routine, to perform linking. What mechanisms exist to initialize variables in a module or kernel during load, hence you want to have NI4BXXX stored in a variable? The manual pages in /usr/src/usr.sbin/i4b/man/ still say that you have to enter a count after "device i4bxxx", instead of using the new "option NI4BXXX=count" to set the number of device units. I think one should keep the "device i4bxxx unit_number" syntax, because then the user is made aware that the device requires a unit number. When the number of device units is unknown, and not directly depending on the number of hardware units present, the kernel should keep a table of settable unit numbers in a special data-section, initialized with default values, reachable by the kernel- and module- loaders ?? --HPS