On Sat, May 14, 2005 at 03:23:53PM -0700, Cheng Jin wrote:
>
> Hi,
>
> Is there a way to compile only kernel modules that one needs like
> with Linux's configuration file? I included only the drivers I
> need in the kernel config file, but all the modules got compiled
> anyway. :(
>
> I looked
Hi,
Is there a way to compile only kernel modules that one needs like
with Linux's configuration file? I included only the drivers I
need in the kernel config file, but all the modules got compiled
anyway. :(
I looked around both in the kernel config dir and google, but didn't
find anything that w
On Aug 15 at 17:23, Bill Moran spoke:
> By the config file. If you enable the module in the config, it is
> built into the kernel, otherwise a kld is generated.
What about `apm'? Is it sufficcient to have it commented out in the
config and set hint.apm.0.disabled=0 and boot with ACPI disabled?
On 2004-08-15 18:04, Hanspeter Roth <[EMAIL PROTECTED]> wrote:
> 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 wh
Hanspeter Roth <[EMAIL PROTECTED]> 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 modul
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?
Can I have
