> cfg80211/nl80211 - overview, get Johannes to disseminate knowledge > because email isn't optimal for this. I haven't had enough time to jump > into it yet, but the fact that Johannes is the vast majority of the > effort here is worrisome. Having a reference implementation (airo, > atmel, maybe libertas) of a fullmac driver ported to cfg80211 would > probably be very useful, even just to get a sense of how the API works. cfg80211/nl80211 is no further for fullmac drivers than a year ago, all work it got so far is for hostapd. I have a fairly decent plan how to add association/... support but it lacks execution because it's completely boring work that doesn't buy us any new features since we still have to support wext. > 802.11n - do we need any discussion here or is it just a question of > executing on the current plan? I think with the last patchset from Ron it's mostly done, cleanups still to do and probably QoS improvements (I'm thinking multiqueue netdevs here) > Userspace MLME - what's going on here? Noise around this seems to be > quieter these days. Is stuff going according to plan/schedule or are > there roadblocks? Nobody is working on this, but a good part is done since hostapd works and the userspace MLME needs many of the same features. Again, the biggest thing is cfg80211/nl80211 support, setting a device to userspace MLME mode and implementing the communication. johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
