On Tuesday 24 October 2006 18:03, Luis R. Rodriguez wrote: > 1. Anyone working on completing FullMAC support on d80211? That doesn't really make sense. Fullmac devices should just use WE or cfg80211 because they, for the most part, do what d80211 does in firmware. There are also strange hybrid devices like ipw2100/ipw2200, but IMHO, it's not worth trying to bolt d80211 onto those devices unless saner firmware becomes available.
> 2. Who's working on a userspace MLME replacement for d80211 and where > are we with that? I think HostAP can handle authentication/association.. or was it wpa-supplicant? Maybe both.. > 3. Who's doing the endianness/smp testing of d80211 and how far are we > with that? The endianness issues seemed fine the last time I checked, and people do seem to be testing BE enough that to uncover an endianness regression I introduced when converting WEP code to use crypto api. As for SMP/locking, I think Jiri Benc knows how to deal with this. > > Lastly, as I have said in previous e-mails -- I agree with a userspace > daemon but where is it and how long before its ready.. also it may be > difficult to introduce as a requirement for distributions and for this > reason I am suggesting going with in-kernel regulatory domain control > and now perhaps in-kernel MLME for a first stable push of d80211, > specially since only... 3 in-kernel drivers currently use d80211! > 4 once p54 is merged, and more to come as I get to them. /me pokes Linville. I think time working on the in-kernel MLME is well worth it since I would like softmac drivers to have feature parity with fullmac drivers. Anything beyond that can go to userspace as far as I'm concerned. (so transitioning to d80211 based drivers won't involve too much pain unless you really want to take advantage of new features) Having some basic regulatory domain control in d80211 in the kernel should be okay for now just to make sure all drivers like the api presented. Working out the details of how to move the d80211 side stuff to userspace should be orthogonal to the driver interface and can be dealt with later, IMHO. -Michael Wu
pgpWGSngKV0AL.pgp
Description: PGP signature
