Actions ======= I need to establish a public git tree for wireless. I would like for this to be on kernel.org, but I haven't got an account established there yet. I've been dragging my feet a little, hoping that the kernel.org account would materialize.
I intend to get the sipsolutions softmac code into the wireless development kernels ASAP. I hope this will spur driver writers that need this functionality to start consolidating on the in-kernel stack. Obviously, what to do with the DeviceScape stack is a pressing issue. I am open to taking patches to introduce the DeviceScape stack on a branch under the (still coming) wireless tree. Obviously, patches that bring features from the DeviceScape stack to the ieee80211 stack would be generally welcome. Since we are toying with the issue of multiple stacks (at least in the wireless development kernels), some thought needs to be done w.r.t. how to make a final decision between the two stacks. An objective lists of functional feature requirements seems like a good place to start. IOW, I would like to have a list of features that would trigger the removal of one stack shortly after the other stack achieves support for the list. Is this feasible? -- John W. Linville [EMAIL PROTECTED] - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
