Re: [Madwifi-devel] Kernel patches.
Status: Beta
Brought to you by:
otaku
From: Terry S. <gal...@ma...> - 2004-03-31 22:46:56
|
Amit, I think the problem here is that some of the MADWifi code is proprietary/non-GPL, which makes putting patches INTO the kernel problematic (at least for the mainstream line). It's more of a political problem than a technical one. The problem isn't getting patches into the MADWifi tree, but patching the MADWifi tree into the kernel tree... At least that's how I read it. I could be wrong. :-) - Terry On Mar 31, 2004, at 3:24 PM, Amit Kucheria wrote: > On Wed, 2004-03-31 at 14:04, Shane Spencer wrote: >> You have your directories in the CVS tree for direct kernel patches of >> the MadWifi driver.. completely blank.. > > I am still not sure what you are referring to. Are you talking about > the > web interface to CVS through sourceforge? > >> I would like to help out.. but concidering the firmware has to be >> loaded.. and isn't GPL.. what then? You have to store the binary HAL >> in >> a file outside of your kernel tree, not compiled in, and load it into >> the module via a non-inline method (which could possibly save on >> memory >> anyways) > > Why is loading modules a problem? All you need to do is download the > code from cvs and if you make any changes/fixes, create a patch and > post > it to the mailing list. If it is good enough, it will be added to the > next release and Sam might even add your name to the "Thank you" list > ;) > >> I wish I were cool enough to work on the 802.11 layer.. I really have >> some interesting thoughts I want to make work as well. > > Its not very difficult if you are up to speed with C. Besides you can > start small. > > -- > .| Amit Kucheria |. > ...| Wireless Systems Engineer |... > .....| Metric Systems Corp., San Diego, CA |..... > ......| www.metricsystems.com |...... > |