Thread: [Madwifi-devel] Making madwifi
Status: Beta
Brought to you by:
otaku
From: Chad M. <cha...@ya...> - 2005-12-31 15:21:03
|
Hi, The madwifi-ng code contains 2 parts: the modules and the userspace command wlanconfig (hopefully soon to be renamed athconfig). I was wondering if anyone has thought about separating these 2 parts into 2 "packages." The purposes of this change would be to enable these external modules to be built with linux kbuild build process - enabling them, IOW, to be automatically built whenever you decide to upgrade the kernel. Sound good? Chad --------------------------------- Yahoo! Shopping Find Great Deals on Holiday Gifts at Yahoo! Shopping |
From: Michael R. <ma...@no...> - 2006-01-02 20:53:49
|
Hi. On Sat, 2005-12-31 at 07:20 -0800, Chad Meister wrote: > The madwifi-ng code contains 2 parts: the modules and the userspace > command wlanconfig (hopefully soon to be renamed athconfig). I was > wondering if anyone has thought about separating these 2 parts into 2 > "packages." The purposes of this change would be to enable these > external modules to be built with linux kbuild build process - > enabling them, IOW, to be automatically built whenever you decide to > upgrade the kernel. > > Sound good? Personally I think this might be a good idea. What do others think? What do you think about the amount of work that this needs to receive? Can you detail what changes would be necessary to get that working? Bye, Mike |
From: Kel M. <ke...@tp...> - 2006-01-03 00:47:40
|
Michael Renzmann wrote: >Hi. > >On Sat, 2005-12-31 at 07:20 -0800, Chad Meister wrote: > > >>The madwifi-ng code contains 2 parts: the modules and the userspace >>command wlanconfig (hopefully soon to be renamed athconfig). I was >>wondering if anyone has thought about separating these 2 parts into 2 >>"packages." The purposes of this change would be to enable these >>external modules to be built with linux kbuild build process - >>enabling them, IOW, to be automatically built whenever you decide to >>upgrade the kernel. >> >>Sound good? >> >> > >Personally I think this might be a good idea. What do others think? > >What do you think about the amount of work that this needs to receive? >Can you detail what changes would be necessary to get that working? > >Bye, Mike > > > Would only be good for when the modules are not absolutely dependent upon the userspace tools. Thanks, Kel. |
From: Chad M. <cha...@ya...> - 2006-01-03 02:49:10
|
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 --- Kel Modderman <ke...@tp...> wrote: > Michael Renzmann wrote: > > >Hi. > > > >On Sat, 2005-12-31 at 07:20 -0800, Chad Meister > wrote: > > > > > >>The madwifi-ng code contains 2 parts: the modules > and the userspace > >>command wlanconfig (hopefully soon to be renamed > athconfig). I was > >>wondering if anyone has thought about separating > these 2 parts into 2 > >>"packages." The purposes of this change would be > to enable these > >>external modules to be built with linux kbuild > build process - > >>enabling them, IOW, to be automatically built > whenever you decide to > >>upgrade the kernel. > >> > >>Sound good? > >> > >> > > > >Personally I think this might be a good idea. What > do others think? > > > >What do you think about the amount of work that > this needs to receive? > >Can you detail what changes would be necessary to > get that working? > > > >Bye, Mike > > > > > > > Would only be good for when the modules are not > absolutely dependent > upon the userspace tools. > > Thanks, Kel. > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do > you grep through log files > for problems? Stop! Download the new AJAX search > engine that makes > searching your log files as easy as surfing the > web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Madwifi-devel mailing list > Mad...@li... > https://lists.sourceforge.net/lists/listinfo/madwifi-devel > __________________________________ Yahoo! for Good - Make a difference this year. http://brand.yahoo.com/cybergivingweek2005/ |
From: Kel M. <ke...@tp...> - 2006-01-03 03:11:43
|
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. |
From: Richard D. <ri...@ph...> - 2006-01-03 21:54:57
|
Hello. Michael Renzmann wrote: > > On Sat, 2005-12-31 at 07:20 -0800, Chad Meister wrote: > >>The madwifi-ng code contains 2 parts: the modules and the userspace >>command wlanconfig (hopefully soon to be renamed athconfig). I was >>wondering if anyone has thought about separating these 2 parts into 2 >>"packages." The purposes of this change would be to enable these >>external modules to be built with linux kbuild build process - >>enabling them, IOW, to be automatically built whenever you decide to >>upgrade the kernel. >> >>Sound good? > > > Personally I think this might be a good idea. What do others think? > > What do you think about the amount of work that this needs to receive? > Can you detail what changes would be necessary to get that working? I spent some time at the weekend upgrading to madwifi-ng. I built some Madwifi rpms where: * the kernel modules are in a kernel_madwifi-ng rpm that builds modules automatically against the current kernel using DKMS <http://linux.dell.com/dkms/>; * the tools are in a madwifi-ng rpm; * madwifi headers are in a madwifi-ng-devel rpm, so I can build wpa_supplicant against whichever madwifi headers I have installed. It all needs polishing up. I want to get madwifi working with WPA enabled on my laptop after booting. Currently it's quite a manual process for me to enable Wifi with WPA using madwifi. Hopefully some of this work can be integrated. DKMS doesn't seem like the one true solution for building the kernel modules. It doesn't help if no compiler is installed, for instance. Would anyone be interested in this work? Bye, Rich =] -- Richard Dawe [ http://homepages.nildram.co.uk/~phekda/richdawe/ ] "You can't evaluate a man by logic alone." -- McCoy, "I, Mudd", Star Trek |
From: Michael R. <ma...@no...> - 2006-01-04 07:08:11
|
Hi. On Tue, 2006-01-03 at 21:54 +0000, Richard Dawe wrote: > I spent some time at the weekend upgrading to madwifi-ng. I built some > Madwifi rpms where: [...] > Would anyone be interested in this work? Yes. For which distribution is that? In addition you might be interested in contacting Patrick Pichon who maintains the madwifi.spec file in the madwifi-ng repository. Bye, Mike |
From: Richard D. <ri...@ph...> - 2006-01-04 20:47:23
|
Hello. Michael Renzmann wrote: > Hi. > > On Tue, 2006-01-03 at 21:54 +0000, Richard Dawe wrote: > >>I spent some time at the weekend upgrading to madwifi-ng. I built some >>Madwifi rpms where: [...] >>Would anyone be interested in this work? > > > Yes. For which distribution is that? Fedora Core 4, but there's nothing particularly Fedora-specific. > In addition you might be interested in contacting Patrick Pichon who > maintains the madwifi.spec file in the madwifi-ng repository. Thanks, will do. (I did examine his spec file before deciding it didn't fit my needs.) Bye, Rich =] -- Richard Dawe [ http://homepages.nildram.co.uk/~phekda/richdawe/ ] "You can't evaluate a man by logic alone." -- McCoy, "I, Mudd", Star Trek |