From owner-freebsd-isdn@FreeBSD.ORG  Sat Feb 26 19:16:58 2005
Return-Path: <owner-freebsd-isdn@FreeBSD.ORG>
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 C786316A4CE
	for <freebsd-isdn@freebsd.org>; Sat, 26 Feb 2005 19:16:58 +0000 (GMT)
Received: from critter.freebsd.dk (f170.freebsd.dk [212.242.86.170])
	by mx1.FreeBSD.org (Postfix) with ESMTP id E9DF243D64
	for <freebsd-isdn@freebsd.org>; Sat, 26 Feb 2005 19:16:57 +0000 (GMT)
	(envelope-from phk@critter.freebsd.dk)
Received: from critter.freebsd.dk (localhost [127.0.0.1])
	by critter.freebsd.dk (8.13.1/8.13.1) with ESMTP id j1QJGti2032009;
	Sat, 26 Feb 2005 20:16:55 +0100 (CET)
	(envelope-from phk@critter.freebsd.dk)
To: hselasky@c2i.net
From: "Poul-Henning Kamp" <phk@phk.freebsd.dk>
In-Reply-To: Your message of "Sat, 26 Feb 2005 20:14:33 +0100."
             <200502262014.36481.hselasky@c2i.net> 
Date: Sat, 26 Feb 2005 20:16:55 +0100
Message-ID: <32008.1109445415@critter.freebsd.dk>
Sender: phk@critter.freebsd.dk
cc: Brooks Davis <brooks@one-eyed-alien.net>
cc: freebsd-isdn@freebsd.org
Subject: Re: mechanical i4b cleanups 
X-BeenThere: freebsd-isdn@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Using ISDN with FreeBSD <freebsd-isdn.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
	<mailto:freebsd-isdn-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isdn>
List-Post: <mailto:freebsd-isdn@freebsd.org>
List-Help: <mailto:freebsd-isdn-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isdn>,
	<mailto:freebsd-isdn-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Feb 2005 19:16:58 -0000

In message <200502262014.36481.hselasky@c2i.net>, Hans Petter Selasky writes:
>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 NI4BXXX constants should just DIE and things be allocated
dynamically as for all other device drivers.

-- 
Poul-Henning Kamp       | UNIX since Zilog Zeus 3.20
phk@FreeBSD.ORG         | TCP/IP since RFC 956
FreeBSD committer       | BSD since 4.3-tahoe    
Never attribute to malice what can adequately be explained by incompetence.