Hi all ! Today I got a connection of libertas + cfg80211 to an AP in the modes WEP40, WEP104, WPA, WPA2 and also with no encryption at all. I still have some loose odds and ends, but the initial work is done and we can consider if we want this feature included in the linux kernel --- or not. However, an cfg80211-converted libertas has some missing features, that others migth think are important: no libertas-mesh, no monitor mode, no ad-hoc mode. Nothing of this is per-se impossible with cfg80211, it just needs to be implemented. I see several possibilities: 1. Let it mature outside --------------------- Keep libertas+cfg80211 out-of-tree until it supports some minimal functionality. Pro: no one misses a feature Cons: no widespread testing of the cfg80211 features 2. Take it as it is ---------------- Nah, not exactly at it is today, but let us stop by missing monitor-mode, adhoc etc --- for now. Implement that later, once libertas is in-kernel and people need it. Pro: widespread testing of the cfg80211 features Cons: people miss some functions when they upgrade the kernel 3. Make things configurable ------------------------ I could create a Kconfig "choice" entry, where one can select CONFIG_LIBERTAS_WEXT or CONFIG_LIBERTAS_CFG80211. I would then provide a bunch of cleanup patches, e.g. to move all things in struct "libertas_private" into one place that are WEXT-related. Pro: no one misses his beloved feature (because it's in CONFIG_LIBERTAS_WEXT) Pro: some people can test the cfg80211-features (with CONFIG_LIBERTAS_CFG80211) Cons: we have a higher amount of #ifdef in Libertas code until either libertas-cfg80211 got all the features added OR until WEXT get's removed from the kernel. -- http://www.holgerschurig.de -- 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
