From owner-freebsd-questions@FreeBSD.ORG Sun Aug 15 21:23:29 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 31EF716A4CE for ; Sun, 15 Aug 2004 21:23:29 +0000 (GMT) Received: from internet.potentialtech.com (h-66-167-251-6.phlapafg.covad.net [66.167.251.6]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0BD3643D2F for ; Sun, 15 Aug 2004 21:23:29 +0000 (GMT) (envelope-from wmoran@potentialtech.com) Received: from working.potentialtech.com (pa-plum-cmts1e-68-68-113-64.pittpa.adelphia.net [68.68.113.64]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by internet.potentialtech.com (Postfix) with ESMTP id 310E569A71; Sun, 15 Aug 2004 17:23:28 -0400 (EDT) Date: Sun, 15 Aug 2004 17:23:27 -0400 From: Bill Moran To: freebsd-questions@freebsd.org Message-Id: <20040815172327.350e31e0.wmoran@potentialtech.com> In-Reply-To: <20040815160407.GA941@gicco.homeip.net> References: <20040815160407.GA941@gicco.homeip.net> Organization: Potential Technologies X-Mailer: Sylpheed version 0.9.12 (GTK+ 1.2.10; i386-portbld-freebsd4.9) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit cc: hampi@rootshell.be Subject: Re: kernel module configuration X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 15 Aug 2004 21:23:29 -0000 Hanspeter Roth wrote: > Hello, > > in the kernel configuration one can enable various devices by the > respective 'device' statement. It seems that most drivers go into > the kernel directly. Some drivers such as 'acpi' produce a kernel > module. > How is determined which modules become built in and which become > modules? By the config file. If you enable the module in the config, it is built into the kernel, otherwise a kld is generated. > Can I have 'ohci' as a kernel module? Whether or not a specific feature is capable of operating as a kernel module or built in is specific to that feature. Some work very well in either capacity (the FAT filesystem drivers for example) others don't really work compiled into the kernel (vinum) and many others _must_ be compiled into the kernel for them to work correctly (ISA and PCI support, I believe) I don't know specifically about ohci, but the man page for ohci would be the first place to check. -- Bill Moran Potential Technologies http://www.potentialtech.com