Comment 51 for bug 37120

Thanks for the detail Andrew.

Would you (or anyone else) happen to know what the ''interface'' used by the wireless command line tools is? I've been snooping around the kernel source, and it looks like the Wireless Extensions interface consists of a bunch of functions with names like ''driver_wx_get_attribute()'' and ''driver_wx_set_attribute()''. For example, the ipw2200 driver has a function name ''ipw_wx_get_essid()'' for retrieving a device's associated ESSID. I figure, there must be a standard set of functions used by the command line tools; it might be as simple as ''wrapping'' those up in some xxx_wx_set_xxx()/xxx_wx_get_xxx() functions (?).