On Fri, 2006-01-13 at 17:19 -0500, John W. Linville wrote: > Configuration > ============= > > Configuration seems to be coalescing around netlink. Among other > things, this technology provides for muliticast requests and > asynchronous event notification. > > The kernel should provide generic handlers for netlink > configuraion messages, and there should be a per-device 80211_ops > (wireless_ops? akin to ethtool_ops) structure for drivers to > populate appropriately.
One other thing: capability. It's not enough to be able to configure the device, user-space tools also have to know what the device is capable of before they try touching it. Ie, which ciphers, protocols, channels, etc. Similar to the IWRANGE ioctl that there is now. Half the problem now is that you can't reliably tell what drivers support which features, or how much they support a particular feature. Think of ethernet devices and whether or not they support carrier detection, there's absolutely no way to tell that now (unless they respond to ethtool or MII, and some cards freeze if you touch them with MII too often). Dan - 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
