From: Pavel Roskin <proski@gn...> - 2007-02-27 22:00:39
Commit 2162 requires CONFIG_KMOD dependency. I don't see why it's
needed. I know users who compile MadWifi statically into the kernel,
and they don't have any problems.
Are you dealing with a compile time problem? May I see the compile
errors? I've just compiled Linux 2.4.34 with MadWifi without any module
support, and there have been no compile errors.
Admittedly, your patch only affects the standalone build, but I don't
see how it's different. The integrated sources can be compiled as a
If it's just a problem because some modules are not loaded
automatically, it's to be expected for the kernels without CONFIG_KMOD.
It's not a bug and it's not something MadWifi should care about. I
think all modules can be loaded into the kernel, in which case the
automatic module loader becomes irrelevant. I just don't see how lack
of CONFIG_KMOD can become a problem.
We may want to require CONFIG_MODULES for the standalone build. Maybe
that's what you meant? Surely MadWifi won't compile for the kernel that
doesn't support modules.
From: Michael Renzmann <madwifi@no...> - 2007-02-28 05:32:29
> Commit 2162 requires CONFIG_KMOD dependency. I don't see why it's
> needed. I know users who compile MadWifi statically into the kernel,
> and they don't have any problems.
Ticket #1167 is related.