> > Well at the moment the cfg80211/nl80211 updates have had a great impact > > on our CVS tree. So it is starting to look like we are going to drop our CVS > > version if we don't find a backwards compatibility for vanilla kernels for it. > > Well, we had to start looking forward somewhere. I wish we'd gotten our > cfg80211 wext-compat hooks into mainline but unfortunately that isn't > so. True, and I was expecting problems like this when I decided to keep supporting vanilla kernels. But at the moment i am just considering what the best options for rt2x00 would be. > > Working the other way around will have a negative (But as mentioned above > > a probably unescapable) side effect. 90% of our testers use the CVS against > > vanilla kernels, and I cannot see them swicthing to the wireless-dev tree. > > So I could switch (it is already under consideration) but it will cost us a lot > > of testers.. :( > > Intel is providing snapshots for this stuff and I think James is still > trying to figure out if there's any chance to provide cfg80211 w/o > patches to mainline, which may just work until critical functionality > mac80211 is moved over to cfg80211 instead of wext. I have seen that package, James is as far with backwards compatibility as we are in rt2x00. But we are apparently hitting against the same problem. But there is some progress I believe, Robin seems to have managed to compile cfg80211 now against a 2.6.20 kernel. So we probably need some research now to add older kernels to the supported list. ;) Ivo - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
