Date: Fri, 4 Dec 1998 15:19:11 +1030 From: Greg Lehey <grog@lemis.com> To: Mike Smith <mike@smith.net.au> Cc: "Justin T. Gibbs" <gibbs@narnia.plutotech.com>, current@FreeBSD.ORG Subject: Re: KLD - what's the idea? Message-ID: <19981204151911.N441@freebie.lemis.com> In-Reply-To: <199812030222.SAA03196@dingo.cdrom.com>; from Mike Smith on Wed, Dec 02, 1998 at 06:22:02PM -0800 References: <199812030213.SAA03115@dingo.cdrom.com> <199812030222.SAA03196@dingo.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wednesday, 2 December 1998 at 18:22:02 -0800, Mike Smith wrote: >>> or to unload unused segments and >>> reload them on the fly during further probe/attach requests (ala Linux). >> >> It would certainly be feasible to arrange for the firmware images to be >> loaded from separate files, should that be an acceptable alternative. >> I'm open to suggestions on how to make this economical and robust... > > I should probably have expanded here; I was thinking for some time > about the usefulness of optionally having two modules associated with a > driver; the core driver code and the 'init' module for the code. You'd > normally put these into two separate files, so for 'foo' you'd > have foo.ko and foo_init.ko. Isn't this something that could be more elegantly handled by different sections in an ELF file? Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981204151911.N441>