John W. Linville wrote:
> Configuration seems to be coalescing around netlink. Among other
> things, this technology provides for muliticast requests and
> asynchronous event notification.
On the other hand, the tree structure of sysfs can handle the
resource exclusivity and sharing naturaly.
A proposal of the layout:
template - template of device that can be created
profile - exclusive set of templates and other resources
plain SoftMAC card:
/sys/class/ieee80211/phy0/profile0/template0/mode # ap
| | /... # ap specific stuff
| |
| *--->/template1/mode # sta
| | /... # sta specific stuff
| |
| *--->/template2/mode # rfmon
| /... # rfmon specific stuff
|
*->/profile
/channel
/txpower
/... # other phy specific stuff
FullMAC card with mode constraints:
/sys/class/ieee80211/phy0/profile0/template0/mode # sta
| /... # sta specific stuff
|
*->/profile1/template0/mode # rfmon
| /... # rfmon specific stuff
|
*->/... # phy specific stuff
virtual interface:
/sys/class/ieee80211/sta0/parent # ->../phy0
/...
card with two chips that share some phy resources:
/sys/class/ieee80211/phy0/txpower # shared txpower
/...
/sys/class/ieee80211/phy1/parent # ->../phy0
/channel # independent
/...
/sys/class/ieee80211/phy2/parent # ->../phy0
/channel # independent
/...
Feyd
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
