From owner-freebsd-hackers Wed Jun 14 13:45:57 2000 Delivered-To: freebsd-hackers@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 4420537C2D1 for ; Wed, 14 Jun 2000 13:45:53 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from semuta.feral.com (semuta [192.67.166.70]) by feral.com (8.9.3/8.9.3) with ESMTP id NAA07675 for ; Wed, 14 Jun 2000 13:45:51 -0700 Date: Wed, 14 Jun 2000 13:45:42 -0700 (PDT) From: Matthew Jacob Reply-To: mjacob@feral.com To: hackers@freebsd.org Subject: loading modules from within the kernel.... Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG There seems to be a number of ways to approach this from within -current, so I thought I'd ask- While I'm configuring a PCI driver, I want to refer to another (possibly loadable) module- I can name it anything I want. It doesn't have any standard entry points- basically, it's a container for firmware for my card that I want to refer to when I'm configuring the PCI driver, and then I can release (and the module can go away after that). If this was Solaris, I would use weak elf binding and some (undocumented) DDI functions to get the kernel linker to pull in the module and satisfy the reference at runtime. What's the right mechanism currently for doing this in FreeBSD-current? A couple of pointers in the right direction would be greatly appreciated. -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message