Date: Sat, 26 Feb 2005 20:14:33 +0100 From: Hans Petter Selasky <hselasky@c2i.net> To: freebsd-isdn@freebsd.org Cc: Brooks Davis <brooks@one-eyed-alien.net> Subject: Re: mechanical i4b cleanups Message-ID: <200502262014.36481.hselasky@c2i.net> In-Reply-To: <20050226004635.GA2922@odin.ac.hmc.edu> References: <20050226004635.GA2922@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200502262014.36481.hselasky>