Date: Sat, 26 Feb 2005 20:16:55 +0100 From: "Poul-Henning Kamp" <phk@phk.freebsd.dk> To: hselasky@c2i.net Cc: freebsd-isdn@freebsd.org Subject: Re: mechanical i4b cleanups Message-ID: <32008.1109445415@critter.freebsd.dk> In-Reply-To: Your message of "Sat, 26 Feb 2005 20:14:33 %2B0100." <200502262014.36481.hselasky@c2i.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?32008.1109445415>