On Tue, Mar 30, 2010 at 11:49:13AM +0200, Holger Schurig wrote: > > If there's any better solution, I'd happily test it. > > Not from me, unfortunately. I'm not really interested into getting full > cfg80211 into Libertas. That is, until either _one_ of this two options > happen: > > * someone that actually uses/wants the proprietary Libertas mesh steps > forward and says "We'll look after this and make it work with cfg80211" > * we remove the proprietary Libertas mesh support > > That is: I won't work on Libertas mesh. I can't justify this time investment > with my employer for something that I'll never need. For my device, my own > version of Libertas + cfg80211 (without any WEXT anymore) works quite nice. > > > So, if neither of the above things happens, then Libertas will work for the > rest of the world with WEXT, as it did before. I don't get your point. The patch I submitted fixes an Ooops in the driver, due to wrong handling of an API. What does that have to do with principle discussions about the frameworks in use? Daniel -- 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
