On Mon, 05 Sep 2005 16:24:41 +0200, Henrik Brix Andersen wrote: > Only a very early version of the ieee80211 header was included in > 2.6.13. This header is not compatible with the ones needed to compile > the current external drivers which depend on ieee80211. This makes it > hard to properly support these external drivers for linux-2.6.13 for > distributions such as Gentoo Linux.
Also, this header (as well as the whole merged "ieee80211 stack") is still ipw-specific. Very invasive changes are needed to turn it into the generic one - so it will become even worse during the time. > I'd rather have waited with the inclusion into mainline until the > ieee80211 subsystem was more mature - but I guess that's another > topic... I definitely agree. But it probably can't be changed now, we have to live with it. Fortunately, the life is not much harder for external drivers developers - they just have to stop to depend on in-kernel ieee80211 header and provide its own. (Heh - isn't this something we tried to avoid?) > I believe the Intel developers are working on a native IEEE 802.11 > wireless stack for the Linux kernel, Intel developers don't seem to work on generic ieee80211 layer. They have bunch of ipw-specific code together with some generic features which they call "ieee80211 stack" and which they seem to be happy with. Sure, recently they added some code - mostly the code needed by their ipw drivers to support QoS and similar features. -- Jiri Benc SUSE Labs - 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
