Date: Sun, 15 Aug 2004 17:23:27 -0400 From: Bill Moran <wmoran@potentialtech.com> To: freebsd-questions@freebsd.org Cc: hampi@rootshell.be Subject: Re: kernel module configuration Message-ID: <20040815172327.350e31e0.wmoran@potentialtech.com> In-Reply-To: <20040815160407.GA941@gicco.homeip.net> References: <20040815160407.GA941@gicco.homeip.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Hanspeter Roth <hampi@rootshell.be> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040815172327.350e31e0.wmoran>