getscanlist command redundant?

[Marcelo Tosatti]

On Thu, Nov 16, 2006 at 03:36:04PM -0800, Frank Huang wrote:
> Marcelo,
> 
> getscanlist will get same result as "iwlist ethx scan" except that
> "iwlist ethX scan" will trigger scanning before result is returned.
> 
> getscantable could get more information (e.g. TSF) than getscanlist. The
> major purpose is for Roaming and CCX, as what Ronak mentioned early.

OK, I've added quality information to getscantable as follows:

-bash-3.1# cat /mnt/libertas_wireless/eth0/getscantable
------------------------------------------------------------------------------
# | ch  | ss  |       bssid       |   cap    |    TSF   | Qual | SSID
------------------------------------------------------------------------------
00| 003 | 039 | 02:16:6f:bb:5e:17 | 0022-A   | aaad1fc4ef | 217 | mynode
01| 006 | 040 | 00:13:46:36:eb:48 | 0401-I   | aaad23637b | 216 | default

-bash-3.1# /root/wlanconfig eth0 getscanlist
Driver build with Wireless Extension 21

BSSID:   02:16:6F:BB:5E:17
SSID:    de
NetMode: ad-hoc
Quality: 217
Privacy: disabled

BSSID:   00:13:46:36:EB:48
SSID:    ult
NetMode: infra
Quality: 216
Privacy: disabled

No of AP's = 2


Privacy is shown as a "P" flag in the "cap" field, when available.

This makes "getscanlist" redundant - it will die together with
wlanconfig. 

Any complaints or comments with reference to that?