Documente Academic
Documente Profesional
Documente Cultură
Johannes Berg
2007-01-20
Overview
1 cfg80211 driver interface 2 userspace interface: nl80211 3 userspace interface: wext compatibility 4 userspace 5 future
Current status
dened in include/net/cfg80211.h cfg80211 register/unregister with priv pointer struct cfg80211 ops for operations on the device virtual device support, identied by struct net device clearly dened commands, each with very limited scope
Current status
dened in include/net/cfg80211.h cfg80211 register/unregister with priv pointer struct cfg80211 ops for operations on the device virtual device support, identied by struct net device clearly dened commands, each with very limited scope
Current status
dened in include/net/cfg80211.h cfg80211 register/unregister with priv pointer struct cfg80211 ops for operations on the device virtual device support, identied by struct net device clearly dened commands, each with very limited scope
Current status
dened in include/net/cfg80211.h cfg80211 register/unregister with priv pointer struct cfg80211 ops for operations on the device virtual device support, identied by struct net device clearly dened commands, each with very limited scope
Operations
Operations
Current status
Current status
Current status
Some details
most operations are commands taking a single argument some MLME attributes are grouped together to allow
Some details
most operations are commands taking a single argument some MLME attributes are grouped together to allow
drivers should just implement cfg80211 the compat layer will thunk wext calls into cfg80211 currently both coexist to allow moving over gradually, a single driver can implement
drivers should just implement cfg80211 the compat layer will thunk wext calls into cfg80211 currently both coexist to allow moving over gradually, a single driver can implement
drivers should just implement cfg80211 the compat layer will thunk wext calls into cfg80211 currently both coexist to allow moving over gradually, a single driver can implement
drivers should just implement cfg80211 the compat layer will thunk wext calls into cfg80211 currently both coexist to allow moving over gradually, a single driver can implement
userspace
no userspace program exists yet libnl needs to be extended once that is done, the netlink interface will be simple to use discussion item: userspace MLME access
userspace
no userspace program exists yet libnl needs to be extended once that is done, the netlink interface will be simple to use discussion item: userspace MLME access
userspace
no userspace program exists yet libnl needs to be extended once that is done, the netlink interface will be simple to use discussion item: userspace MLME access
userspace
no userspace program exists yet libnl needs to be extended once that is done, the netlink interface will be simple to use discussion item: userspace MLME access
future
802.11w is upcoming and we will want a userspace MLME cfg80211/nl80211 will provide access to the MAC for the
userspace MLME
cfg80211/nl80211 also needs to provide MLME access for
full-MAC cards
need to dene notication
future
802.11w is upcoming and we will want a userspace MLME cfg80211/nl80211 will provide access to the MAC for the
userspace MLME
cfg80211/nl80211 also needs to provide MLME access for
full-MAC cards
need to dene notication
future
802.11w is upcoming and we will want a userspace MLME cfg80211/nl80211 will provide access to the MAC for the
userspace MLME
cfg80211/nl80211 also needs to provide MLME access for
full-MAC cards
need to dene notication
future
802.11w is upcoming and we will want a userspace MLME cfg80211/nl80211 will provide access to the MAC for the
userspace MLME
cfg80211/nl80211 also needs to provide MLME access for
full-MAC cards
need to dene notication
future
discussion item
I believe that we need a way to transparently access the MLME. Should this be a userspace library or should the kernel arbitrate? userspace pro:
no kernel/userspace transistion necessary
kernel pro:
nl80211 can be used kernel just forwards messages to
10
11