Re: [Madwifi-devel] Making madwifi

[Kel M. <ke...@tp...>]

Chad Meister wrote:

>Hi,
>
>Kel is right, but I thought perhaps the question is
>the other way around.  Instead of how dependent the
>modules are on the userspace tools, the question is
>how dependent are the userspace tools on the modules. 
>The modules should only need code from the kernel to
>compile (in theory).  The userspace should strongly
>depend upon the madwifi code, rather than the kernel
>(in theory).
>
>Whether or not that is the case, I have no idea, since
>I haven't poked in the code and would defer to the
>experts; namely, you all.  Once that level of
>difficulty is determined, the next step would be to
>follow the kbuild docs accompanying the kernel source
>which describes the process of building external
>modules along with the kernel modules.
> 
>Chad
>
>  
>

The tools themselves have been made self-contained by Pavel Roskin. 
Please see these changesets for more details:-

http://madwifi.org/changeset/1325
http://madwifi.org/changeset/1341
http://madwifi.org/changeset/1342
http://madwifi.org/changeset/1343
http://madwifi.org/changeset/1345
http://madwifi.org/changeset/1350

Usually kbuild is suitable for modules that are wanting to be in the 
kernel, I don't think that is ever the case with madwifi in its current 
state. Anyhow, your distribution should provide some mechanism of 
compiling external modules along with your new kernel.

Thanks, Kel.