On Sun, 2007-06-17 at 11:29 -0400, Dan Williams wrote:
> NM uses wpa_supplicant for 3 basic things:
<snip good explanation, thanks>
> I like pushing most of the config stuff to wpa_supplicant, because that
> basically means that all of that is in _one_ project. When
> nl80211/cfg80211 land and start getting adopted, that means that only
> _one_ of {NM, wpa_supplicant} needs to get ported over, instead of two.
I can understand that. I guess I'm still dreaming of some sort of ideal
world where NM and wpa_supplicant use nl80211 to communicate so that it
is easier to use a different userspace MLME maybe, or maybe just have
another program like 'iw' work together with the whole lot easily as
well.
johannes
Attachment:
signature.asc
Description: This is a digitally signed message part
