Re: nl80211 status? (implying cfg80211 status)

[Johannes Berg <johannes@sipsolutions.net>]

[-- Attachment #1: Type: text/plain, Size: 943 bytes --]

On Tue, 2007-06-05 at 12:53 +0200, Johannes Berg wrote:

> > As far as I understand, the first thing to tackle is converting
> > everything to cfg80211 and making wext call cfg80211 functions,
> > putting all the compatibility cruft into that layer while at it.
> 
> I wouldn't necessarily start with that.

I should've elaborated here.

What I'd do if I had time now is add things to nl80211/cfg80211 and then
implement the calls in mac80211 (or a fullmac driver of your choice.)
Then write the appropriate userspace tool for testing and see if it
works, i.e. you can associate, do key operations etc. Use WEP for now,
and then maybe modify wpa_supplicant too for nl80211. Then, at some
point, you have wpa_supplicant working on mac80211 (or the driver). Then
in theory you don't need wext any more, and as an afterthought you can
still add wext compatibility so the deprecated wireless tools continue
to work.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 190 bytes --]