mechanical i4b cleanups

Hans Petter Selasky hselasky at
Sat Feb 26 19:13:55 GMT 2005

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:
> -- 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 ??


More information about the freebsd-isdn mailing list