Hi, On Fri, Jan 13, 2006 at 05:03:28PM -0600, Chase Venters wrote: > On Friday 13 January 2006 15:32, John W. Linville wrote: > > What about the suggestion of having both stacks in the kernel at once? > > I'm not very excited about two in-kernel stacks. Still, consolidating > > wireless drivers down to two stacks is probably better than what we > > have now...? Either way, we would have to have general understanding > > that at some point (not too far away), one of the stacks would have > > to disappear. > > But I have to NAK the idea of two stacks. There are implications in the 'here > and now', so to speak, but what worries me the most is long term. You know > how it's no fun fixing bugs when you could be adding new features? Let's say > that on May 2006, you drop the hammer and decide that Stack B is the winner. > You've now got to convince / motivate the Stack A users to stop what they're > doing and work hard to migrate to Stack B.
At the present time, the ieee80211 stack is used by ipw2x00 (heavily) and hostap (a little bit). Other mainline drivers only use headers (mainly constants). If it shows that the DeviceScape stack is more mature and appropriate (which I think it is), I don't see anything wrong with having both in the kernel at one time time. - DeviceScape can be there so it can be polished and new drivers can start using it. - ieee80211 could be there with a big fat warning that it will go away soon, just to allow ipw2x00 to work while DeviceScape and the ipw2x00 port for it to be stabilized. Isnt't this a viable option? Regards, -- Jirka Bohac <[EMAIL PROTECTED]> SUSE Labs, SUSE CR - 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
